Updated: October 28, 2024 |
The following example shows a configuration file for a guest running in a VM created by a qvm process.
system qnx7-x86_64-guest ram 0xa0000 rom 0xc0000,0x40000 ram 1024M # Specify "cpu" for each vCPU you want to assign to your guest cpu cpu load /vm/images/qnx7-x86_64-guest.ifs vdev ioapic loc 0xf8000000 intr apic name myioapic vdev ser8250 intr myioapic:4 name ser8250_0 vdev timer8254 intr myioapic:0 name timer8254_0 vdev mc146818 name mc146818_0 vdev shmem name shmem_0 vdev pckeyboard name pckeyboard_0 # An example network device. Connects to a peer named vp0 in the host. # This peer is found at /dev/vdevpeers in the host. vdev virtio-net name ptp peer /dev/vdevpeers/vp0 # An example block device. This file has to be created somewhere; # in this case, it's created in the IFS with dd. vdev virtio-blk hostdev /dev/qvmdisk0 name virtio-blk_qvmdisk0 # 8259s are here for legacy systems only. # They only take the 'loc' option. vdev 8259 loc 0x20 vdev 8259 loc 0xa0 vdev hpet loc 0xf8008000 intr myioapic:2 name hpet_0
We know that this configuration is for an x86 VM because 8259 devices and APIC are supported only on that architecture.
The name property is specified for the vdevs so they appear under /dev/qvm/system_name/vdev_name. In this case, system_name is qnx7-x86_64-guest.