You are not logged in.
Pages: 1
Topic closed
I am trying to setup a windows10 VM with libvirt but windows doesn't recognized my GPU and the driver installation fails.
Here are some info:
$ dmesg | grep -e DMAR -e IOMMU
[ 0.000000] ACPI: DMAR 0x000000009CFD9000 0000B8 (v01 LENOVO CB-01 00000001 ACPI 00040000)
[ 0.000000] DMAR: IOMMU enabled
[ 0.024777] DMAR: Host address width 39
[ 0.024778] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.024785] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
[ 0.024785] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.024788] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008020660462 ecap f010da
[ 0.024789] DMAR: RMRR base: 0x0000009cdf0000 end: 0x0000009ce0ffff
[ 0.024790] DMAR: RMRR base: 0x0000009d800000 end: 0x0000009f9fffff
[ 0.024792] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.024793] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.024793] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.025157] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 4.076584] DMAR: No ATSR found
[ 4.076622] DMAR: dmar0: Using Queued invalidation
[ 4.076628] DMAR: dmar1: Using Queued invalidation
[ 4.076704] DMAR: Setting RMRR:
[ 4.076776] DMAR: Setting identity map for device 0000:00:02.0 [0x9d800000 - 0x9f9fffff]
[ 4.077039] DMAR: Setting identity map for device 0000:00:14.0 [0x9cdf0000 - 0x9ce0ffff]
[ 4.077097] DMAR: Setting identity map for device 0000:00:1a.0 [0x9cdf0000 - 0x9ce0ffff]
[ 4.077158] DMAR: Setting identity map for device 0000:00:1d.0 [0x9cdf0000 - 0x9ce0ffff]
[ 4.077178] DMAR: Prepare 0-16MiB unity mapping for LPC
[ 4.077222] DMAR: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[ 4.077364] DMAR: Intel(R) Virtualization Technology for Directed I/O
[ 10.539548] [drm] DMAR active, disabling use of stolen memory$ ./test_iommu.sh
IOMMU Group 0 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06)
IOMMU Group 10 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d5)
IOMMU Group 11 00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [8086:8c18] (rev d5)
IOMMU Group 12 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05)
IOMMU Group 13 00:1f.0 ISA bridge [0601]: Intel Corporation HM86 Express LPC Controller [8086:8c49] (rev 05)
IOMMU Group 13 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05)
IOMMU Group 13 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05)
IOMMU Group 14 08:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)
IOMMU Group 15 09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)
IOMMU Group 16 0a:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5249 PCI Express Card Reader [10ec:5249] (rev 01)
IOMMU Group 1 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
IOMMU Group 1 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 860M] [10de:1392] (rev a2)
IOMMU Group 2 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
IOMMU Group 3 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
IOMMU Group 4 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)
IOMMU Group 5 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
IOMMU Group 6 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05)
IOMMU Group 7 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05)
IOMMU Group 8 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5)
IOMMU Group 9 00:1c.1 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 [8086:8c12] (rev d5)$cat test_iommu.sh
#!/bin/bash
shopt -s nullglob
for d in /sys/kernel/iommu_groups/*/devices/*; do
n=${d#*/iommu_groups/*}; n=${n%%/*}
printf 'IOMMU Group %s ' "$n"
lspci -nns "${d##*/}"
done$ modinfo vfio-pci
filename: /lib/modules/4.14.7-1-ARCH/kernel/drivers/vfio/pci/vfio-pci.ko.xz
description: VFIO PCI - User Level meta-driver
author: Alex Williamson <alex.williamson@redhat.com>
license: GPL v2
version: 0.2
srcversion: DB8F55EC2187EC83F7E71EA
depends: vfio,irqbypass,vfio_virqfd
intree: Y
name: vfio_pci
vermagic: 4.14.7-1-ARCH SMP preempt mod_unload modversions
parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask]]]]" and multiple comma separated entries can be specified (string)
parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-pci@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool)
parm: disable_vga:Disable VGA resource access through vfio-pci (bool)
parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool)$ cat /etc/modprobe.d/vfio.conf
options vfio-pci ids=10de:1392$ cat /etc/mkinitcpio-vfio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=(vfio vfio_iommu_type1 vfio_pci vfio_virqfd)
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=()
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()dmesg | grep -i vfio
[ 0.000000] Command line: initrd=\intel-ucode.img initrd=\vfio-linux.img root=PARTUUID=4883aa58-cc8b-4673-b2ee-f8ba29409fde rw intel_iommu=on
[ 0.000000] Kernel command line: initrd=\intel-ucode.img initrd=\vfio-linux.img root=PARTUUID=4883aa58-cc8b-4673-b2ee-f8ba29409fde rw intel_iommu=on
[ 4.169623] VFIO - User Level meta-driver version: 0.3
[ 4.186828] vfio_pci: add [10de:1392[ffff:ffff]] class 0x000000/00000000
[ 142.927966] vfio-pci 0000:01:00.0: enabling device (0002 -> 0003)
[ 143.964826] vfio_ecap_init: 0000:01:00.0 hiding ecap 0x1e@0x258
[ 143.964836] vfio_ecap_init: 0000:01:00.0 hiding ecap 0x19@0x900
[ 156.159103] vfio-pci 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x0000$ lspci -nnk -d 10de:1392
01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 860M] [10de:1392] (rev a2)
Kernel driver in use: vfio-pci
Kernel modules: nouveau, nvidia_drm, nvidia/etc/libvirt/qemu.conf
nvram = [
"/usr/share/ovmf/ovmf_code_x64.bin:/usr/share/ovmf/ovmf_vars_x64.bin",
]$ sudo cat win10.xml
[sudo] password for guillaume:
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
virsh edit win10
or other application using the libvirt API.
-->
<domain type='kvm'>
<name>win10</name>
<uuid>8b5b0925-e38c-490e-bc8b-ebd7d8fdeca5</uuid>
<memory unit='KiB'>6291456</memory>
<currentMemory unit='KiB'>6291456</currentMemory>
<vcpu placement='static'>8</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/ovmf/ovmf_code_x64.bin</loader>
<nvram>/var/lib/libvirt/qemu/nvram/win10_VARS.fd</nvram>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<relaxed state='on'/>
<vapic state='on'/>
<spinlocks state='on' retries='8191'/>
</hyperv>
<vmport state='off'/>
</features>
<cpu mode='host-passthrough' check='none'/>
<clock offset='localtime'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
<timer name='hypervclock' present='yes'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<pm>
<suspend-to-mem enabled='no'/>
<suspend-to-disk enabled='no'/>
</pm>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/var/lib/libvirt/images/win10.qcow2'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/home/guillaume/Download/Win10_1607_English_x64.iso'/>
<target dev='hdb' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='usb' index='0' model='ich9-ehci1'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x7'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci1'>
<master startport='0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci2'>
<master startport='2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci3'>
<master startport='4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='virtio-serial' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</controller>
<interface type='direct'>
<mac address='52:54:00:a2:8f:61'/>
<source dev='enp9s0' mode='bridge'/>
<model type='rtl8139'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<serial type='pty'>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes'>
<listen type='address'/>
</graphics>
<sound model='ich6'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</sound>
<video>
<model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</source>
<rom bar='on'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</hostdev>
<redirdev bus='usb' type='spicevmc'>
<address type='usb' bus='0' port='2'/>
</redirdev>
<redirdev bus='usb' type='spicevmc'>
<address type='usb' bus='0' port='3'/>
</redirdev>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</memballoon>
</devices>
</domain>Offline
GPU passthrough is not as simple as other pci devices ---- and especially for NVIDIA.
And passthrough to only a discrete GPU on laptop(exp. GeForce GTX 860M) is useless,
In this case you should use intel GVT-g, described there
https://01.org/igvt-g
and then try to connect to the discrete GPU using the virtual intel GPU.
Last edited by yw662 (2017-12-25 07:28:20)
Offline
I have the same gpu but in different laptop brand MSI, what I did to do passthrough in libvirt was :
- Download the gpu rom from the support page,
- Copy it to /usr/share/qemu
- Modify qemu.conf according to wiki (nvram, cgroup_device_acl)
- Create the VM in virt-manager, adding only PCI Host device (the GPU 0000:01:00.0 )
- With virsh edit the xml of the VM and added the following (schema domain, kvm hidden, rombar file pointing to gpu bios and gpu vendor parameters to qemu):
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
...
<features>
...
<kvm>
<hidden state='on'>
</kvm>
...
</features>
...
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</source>
<rom bar='on' file='/usr/share/qemu/GTX860M.rom'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0' multifunction='on'/>
</hostdev>
...
</devices>
<qemu:commandline>
<qemu:arg value='-set'/>
<qemu:arg value='device.hostdev0.x-pci-sub-vendor-id=5218'/>
<qemu:arg value='-set'/>
<qemu:arg value='device.hostdev0.x-pci-sub-device-id=4354'/>
</qemu:commandline>sub-vendor-id : 5218 and sub-device-id:4352 is the decimal values of what lspci -nnk 01:00 shows of the GPU (10de:119a).
01:00.0 3D controller [0302]: NVIDIA Corporation GK104M [GeForce GTX 860M] [10de:119a] (rev ff)
Kernel modules: nouveau, nvidia_drm, nvidi- I bind it with this script so I dont have to put it on modprobe the id's (sudo ./vfio-bind.sh 000:01:00.0)
#!/bin/bash
modprobe vfio-pci
for dev in "$@"; do
vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
device=$(cat /sys/bus/pci/devices/$dev/device)
if [ -e /sys/bus/pci/devices/$dev/driver ]; then
echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
fi
echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
doneWith that the latest driver install ok, without error (no code 43) : https://imgur.com/a/MS45H
The problem is that the nvidia control panel complains that it needs an attached monitor, I dont have one available now (I'm travelling) but I tried with remotefx in Windows Guest and it recognizes the gpu but the fps are very low (max 30-35) in unigine: https://imgur.com/fv43nJXl.png , haven' t tested any game yet.
hope it helps .
Last edited by gnox (2017-12-25 00:32:21)
Offline
The problem is that the nvidia control panel complains that it needs an attached monitor, I dont have one available now (I'm travelling) but I tried with remotefx in Windows Guest and it recognizes the gpu but the fps are very low (max 30-35) in unigine: https://imgur.com/fv43nJXl.png , haven' t tested any game yet.
That is why I say passthrough to a discrete GPU is useless.
Last edited by yw662 (2017-12-25 07:25:48)
Offline
I have the same gpu but in different laptop brand MSI, what I did to do passthrough in libvirt was :
- Download the gpu rom from the support page,
- Copy it to /usr/share/qemu
- Modify qemu.conf according to wiki (nvram, cgroup_device_acl)
- Create the VM in virt-manager, adding only PCI Host device (the GPU 0000:01:00.0 )
- With virsh edit the xml of the VM and added the following (schema domain, kvm hidden, rombar file pointing to gpu bios and gpu vendor parameters to qemu):
.
I can't find the gpu rom on the support page, could you provide a link?
Offline
gnox wrote:I have the same gpu but in different laptop brand MSI, what I did to do passthrough in libvirt was :
- Download the gpu rom from the support page,
- Copy it to /usr/share/qemu
- Modify qemu.conf according to wiki (nvram, cgroup_device_acl)
- Create the VM in virt-manager, adding only PCI Host device (the GPU 0000:01:00.0 )
- With virsh edit the xml of the VM and added the following (schema domain, kvm hidden, rombar file pointing to gpu bios and gpu vendor parameters to qemu):
.I can't find the gpu rom on the support page, could you provide a link?
You can use gpu-z to copy the rom.
Offline
You can use gpu-z to copy the rom.
GPU-z seems to be a windows only program. I tried to extract the GPU rom with nvflash but I get the following error
$ sudo ./nvflash --save 860m.rom
NVIDIA Firmware Update Utility (Version 5.414.0)
Simplified Version For OEM Only
Adapter: GeForce GTX 860M (10DE,1392,17AA,3978) H:--:NRM S:00,B:01,D:00,F:00
Identifying EEPROM...
Command complete with error, Error code = 0x0003
Command id: 0x0000002 Command: NV_UCODE_CMD_COMMAND_EID failed
Command Status: NV_UCODE_CMD_STS_NONE
Error Code= 0x00000003: NV_UCODE_ERR_CODE_CMD_EID_RD_ERROR
EEPROM ID process failed.
ERROR: Error: Display adapter's EEPROM ID process failedOffline
I know that this is an old thread, but it's the only place I find an explanation of one of the essential steps.... but I find the explanation incomprehensible. If i understood it, i could fix my problem. Please explain:
In post #3, gnox advised
... gpu vendor parameters to qemu):
<qemu:commandline> <qemu:arg value='-set'/> <qemu:arg value='device.hostdev0.x-pci-sub-vendor-id=5218'/> <qemu:arg value='-set'/> <qemu:arg value='device.hostdev0.x-pci-sub-device-id=4354'/> </qemu:commandline>sub-vendor-id : 5218 and sub-device-id:4352 is the decimal values of what lspci -nnk 01:00 shows of the GPU (10de:119a).
01:00.0 3D controller [0302]: NVIDIA Corporation GK104M [GeForce GTX 860M] [10de:119a] (rev ff) Kernel modules: nouveau, nvidia_drm, nvidi
I feel i must be very stupid to note that 0x10de is 4318 in decimal, NOT 5218. and 0x119a is 4506 in decimal, NOT 4352. So what exactly does one do to go from the output of lspci -nnk that gnox quotes to the <qemu;arg value=... /> lines for sub-vendor-id and sub-device-id in the domain xml?
I note that in my case, the output of lspci -nnk includes the following:
$ lspci -nnk
...
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1)
Subsystem: Dell GP106M [GeForce GTX 1060 Mobile] [1028:0802]
Kernel driver in use: vfio-pci
Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation GP106 High Definition Audio Controller [10de:10f1] (rev a1)
Subsystem: Dell GP106 High Definition Audio Controller [1028:0802]
Kernel driver in use: vfio-pci
Kernel modules: snd_hda_intel
....Is it the numbers on the **subsystem** line (which gnox doesn't mention in his post) that I am supposed to write in decimal on the <qemu:arg value=.../> lines? I see that these numbers (in my case [1028:0802]) are the same for the video controller and the the audio device. So is it correct that I only write them once, as follows:
<qemu:commandline>
<qemu:arg value='-set'/>
<qemu:arg value='device.hostdev0.x-pci-sub-vendor-id=4136'/>
<qemu:arg value='-set'/>
<qemu:arg value='device.hostdev0.x-pci-sub-device-id=2050'/>
</qemu:commandline>(because 0x1028=4136 and 0x802=2050) ??
I only hope that I'm not so hopelessly confused that no one has the stomach to try to set me straight.
With thanks,
scott
Offline
Please do not necrobump. Start a new thread with your issue and link back to this one if you think it still applies.
Closing.
Offline
Pages: 1
Topic closed