#!/bin/bash
# Check if there are any examples or tests that show how VirtualMachine is used
echo "=== Searching for VirtualMachine usage patterns ==="
rg -n -C3 -t go "VirtualMachine" --exclude-dir=vendor

echo -e "\n=== Checking for any consumers of the Memory field specifically ==="
rg -n -C3 -t go "\.Memory" --exclude-dir=vendor

echo -e "\n=== Looking for any go.mod files that might depend on this package ==="
fd -t f "go.mod" -x cat {} \;

echo -e "\n=== Checking for any existing imports of strongunits in the codebase ==="
rg -n -t go "strongunits" --exclude-dir=vendor

#!/bin/bash
# Fix the ripgrep syntax and search for usage patterns
echo "=== Searching for VirtualMachine usage patterns ==="
rg -n -C3 -t go "VirtualMachine" -g '!vendor/**'

echo -e "\n=== Checking for any consumers of the Memory field specifically ==="
rg -n -C3 -t go "\.Memory" -g '!vendor/**'

echo -e "\n=== Checking for any existing imports of strongunits in the codebase ==="
rg -n -t go "strongunits" -g '!vendor/**'

echo -e "\n=== Looking for any test files that might show usage patterns ==="
rg -n -C3 -t go -g '*test*.go' "VirtualMachine\|strongunits"

#!/bin/bash
# Let's try a simpler approach without complex glob patterns
echo "=== Listing Go files to understand structure ==="
find . -name "*.go" -type f | head -20

echo -e "\n=== Searching for VirtualMachine usage patterns ==="
rg -n -C3 "VirtualMachine"

echo -e "\n=== Checking for any consumers of the Memory field specifically ==="
rg -n -C3 "\.Memory"

echo -e "\n=== Checking for any existing imports of strongunits in the codebase ==="
rg -n "strongunits"

echo -e "\n=== Looking for external dependencies on this package ==="
# Check if there are any GitHub references or import statements that would indicate external usage
rg -n "github.com/crc-org/vfkit"

#!/bin/bash
# Let's search for external usage of this vfkit package to understand the downstream impact
echo "=== Searching for potential external dependencies using GitHub search simulation ==="
echo "This would show projects that might depend on github.com/crc-org/vfkit/pkg/config"

echo -e "\n=== Let's check if there are any examples of strongunits.B being used in exported APIs ==="
rg -n -C2 "strongunits\.B"

echo -e "\n=== Let's check what strongunits types are actually exported from the VirtualMachine struct ==="
echo "Looking at the VirtualMachine struct definition:"
rg -n -A10 -B2 "type VirtualMachine struct"

echo -e "\n=== Let's check if the JSON marshaling preserves compatibility ==="
rg -n -C3 "memoryBytes"

How does crc-org/crc project use vfkit VirtualMachine Memory field strongunits

crc-org/crc vfkit import usage "github.com/crc-org/vfkit/pkg/config" VirtualMachine

"github.com/crc-org/vfkit/pkg/config"

// create VM with 4 vCPUs and 4096 MiB RAM
vm := config.NewVirtualMachine(4, 4096, boot)

// add devices as needed, e.g. virtio block / network (use provided constructors)
// err := vm.AddDevice(config.VirtioBlockNew("disk0", "/path/to/disk.img"))
// handle err...

// produce exec.Cmd for vfkit binary (path to vfkit)
cmd, err := vm.Cmd("/usr/local/bin/vfkit")
if err != nil {
	fmt.Fprintf(os.Stderr, "cmd: %v\n", err)
	os.Exit(1)
}

// run vfkit
cmd.Stdout = os.Stdout
cmd.Stderr = os.Stderr
if err := cmd.Run(); err != nil {
	fmt.Fprintf(os.Stderr, "run: %v\n", err)
	os.Exit(1)
}

podman crc vfkit "strongunits.B" "Memory" field usage breaking change