January 15, 201610 yr Ok i don't know if this has been answered or not but haven't had any luck searching. I have a PXE server setup on the network. if i boot the physical machine it will pxe boot. but when i create a VM and try to get it to do the same it will not. i have the bridge reconfigured so that VM's pull an ip from the network not from unraid. i assume this is something super simple but i can't figure it out. below is the XML for my basic test vm. <domain type='kvm'> <name>pxe test</name> <uuid>8f024a2f-0e9a-cfff-cd4b-3d0cc474c141</uuid> <metadata> <vmtemplate name="Custom" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disk1/vmachine/pxe test/vdisk1.img'/> <target dev='hda' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:c8:b7:e9'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/pxe test.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> Thanks in advance for any help and suggestions
January 16, 201610 yr Go into Settings --> Network Settings and change the 'Bridge forward delay' to something other than 0 (I use 4). See here for more detail: http://lime-technology.com/forum/index.php?topic=41079.msg388899#msg388899 More info here: http://lime-technology.com/forum/index.php?topic=41381.0 John
January 16, 201610 yr Author The problem isn't time out it's that it doesn't seem to try for an IP for pxe boot Screenshot attached
January 16, 201610 yr Two things...You need to add the NIC to the boot order: <interface type='bridge'> <mac address='52:54:00:d9:d5:39'/> <source bridge='br0'/> <model type='virtio'/> <boot order='1'/> </interface> If it still fails, you may also need to specify a different NIC driver other than virtio (i.e. e1000): <interface type='bridge'> <mac address='52:54:00:d9:d5:39'/> <source bridge='br0'/> <model type='e1000'/> <boot order='1'/> </interface>
January 16, 201610 yr Author that was the problem johnodon. thank you so much for the help. i'm used to vmware/esxi where that is kind of a given. that and it has a bios that you can get into to set that stuff.
March 16, 20188 yr On 1/16/2016 at 4:58 PM, johnodon said: Two things...You need to add the NIC to the boot order: <interface type='bridge'> <mac address='52:54:00:d9:d5:39'/> <source bridge='br0'/> <model type='virtio'/> <boot order='1'/> </interface> If it still fails, you may also need to specify a different NIC driver other than virtio (i.e. e1000): <interface type='bridge'> <mac address='52:54:00:d9:d5:39'/> <source bridge='br0'/> <model type='e1000'/> <boot order='1'/> </interface> And how can I do it for the nic that I have passthrough?, I have introduced some boot order commands but it doesn't work. IOMMU group 14: [8086:1521] 05:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) IOMMU group 15: [8086:1521] 05:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) <domain type='kvm' id='5'> <name>pfSense</name> <uuid>863d8c24-04f2-accd-72d8-260a5d6b2afb</uuid> <metadata> <vmtemplate xmlns="unraid" name="FreeBSD" icon="freebsd.png" os="freebsd"/> </metadata> <memory unit='KiB'>2621440</memory> <currentMemory unit='KiB'>2621440</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.11'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISO/pfSense-CE-2.4.2-RELEASE-amd64.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VMDisks/pfSense/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:3f:56:10'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <boot order='5'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-5-pfSense/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='es'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <boot order='6'/> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </source> <boot order='7'/> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
April 12, 20206 yr Quote <interface type='bridge'> <mac address='52:54:00:d9:d5:39'/> <source bridge='br0'/> <model type='e1000'/> <boot order='1'/> </interface> This worked for me as well but another change I needed to make was using SeaBIOS becuase I was getting the shell terminal on Boot. I used this with the docker network.xyz container. You can also boot from a Network Controller being passed in just by adding <boot order='2'/> For my use I removed the bridge interface and used a passed in LAN card. Thanks Edited April 12, 20206 yr by Dallas.toth
July 22, 20205 yr On 4/13/2020 at 12:06 AM, Dallas.toth said: This worked for me as well but another change I needed to make was using SeaBIOS becuase I was getting the shell terminal on Boot. I used this with the docker network.xyz container. You can also boot from a Network Controller being passed in just by adding <boot order='2'/> For my use I removed the bridge interface and used a passed in LAN card. Thanks I have the same issue, i have to use seabios as with OVMF I get pxe-e09 could not allocate i/o buffers errors.
March 4, 20224 yr So im trying to play with WDS setup. I have successfully set up a WDS server in a VM (lets call it Server1), which can be reached and works no problem on bare metal machines in the same network. Where im stuck is I try to set up another Windows VM which could reach Server1 and install OS from it. Based on the above advice, i have added the below code into the xml file. <interface type='bridge'> <mac address='52:54:00:d9:d5:39'/> <source bridge='br0'/> <model type='virtio'/> <boot order='1'/> </interface> The PXE is is picking up the Server1, and the install process starts.... and then it stops with the following error: "WDSclient: an error occured while trying to obtain an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment". Read on interwebs this might be a driver issue. If someone has encountered the same problem and care to share a solution, you're most welcomed. Thanks.
March 4, 20224 yr 8 minutes ago, Januszmirek said: "WDSclient: an error occured while trying to obtain an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment". Never tried, so these are only suggestions. I think too that's the issue is missing driver. I would try these two options: 1. add driver package to wds, the drivers of the emulated network card are into the separate virtio iso image which you can download for free; windows doesn't include any virtio driver. OR 2. I would try to change the virtio model type, I think drivers should be builtin if using for example: <model type='e1000-82545em'/>
March 4, 20224 yr 9 minutes ago, ghost82 said: 2. I would try to change the virtio model type, I think drivers should be builtin if using for example: <model type='e1000-82545em'/> Genius, worked like a charm. Thanks!;)
March 5, 20224 yr 22 hours ago, ghost82 said: 2. I would try to change the virtio model type, I think drivers should be builtin if using for example: <model type='e1000-82545em'/> Genius, worked like a charm. Thanks!;) Ok, I won't be starting a new topic as I hope you guys can help me out with this one too. So as a part of messing around with WDS I am at the point where I finished setting up a 'windows10' (set up as a VM on unraid) and now I need to capture it into a single .wim file (using dism command) that is then used to create golden Windows 10 image than you can install on number of machines over PXE. You can usually do this using WindowsPE tool or by booting into PXE on WDS server. With bare metal machines this works like a charm. Because when I use a bare metal machine and boot to PXE I still have access to my "C:\" drive on that machine to be able to capture it into an image (.wim file). The issue I an encountering is the way VMs work on Unraid: I was able to edit the windows10 VM .xml to include booting into either PXE (Thanks @ghost82) or into WindowsPE.iso. This works just fine. However the problem is that at this point the actual virtual disk (.img file) with my windows10 is not mounted yet. And therefore I can not capture it;(. So the question is: how do I mount that .img file created in unraid so that PXE or WinPE can have access to it, so I can capture it with dism command? Hope that is roughly clear but if I did not give enough details, just let me know and I will. Thanks again;)
March 5, 20224 yr 2 hours ago, Januszmirek said: how do I mount that .img file created in unraid so that PXE or WinPE can have access to it, so I can capture it with dism command? Hope that is roughly clear but if I did not give enough details, just let me know and I will. Thanks again;) I'm quite sure you explained well, however I never did such things, so if you could explain more into details it will help, and maybe someone else can reply instead of only people who managed with wds/pxe etc. What I understood is only that you have a windows 10 vm up and running into unraid. What you want to do next is confusing for me, but it's probably my fault! Can you specify which tools you use on bare metal, which are the physical machines involved (for ex: you have a machine with win10, you have a wds server, you have another third party pc, ?) and how the workflow works (with commands/instructions). Thanks
March 5, 20224 yr So I don't want to use bare metal as for my needs it is not preferable and have it own issues, that are beside the point. I would want to use VM1 (Server with Windows server 2019 with WDS) and a VM2 (Client with Windows 10). Both of these are currently set up on my unraid as separate VMs. When I set up VM2, I edited the xml to define certain boot order. In my case it is 1. network boot (booting into PXE on VM1), and 2. booting into .img file with VM2. The problem is that when you boot into 1. (PXE), you don't have access to virtual disk of VM2 (.img). And therefore you can't capture that image. To put it into perspective and give you an example: when you use bootable USB drive with say linux distro on your laptop, you still have access not only to files on your USB stick but most importantly to your ssd disk in your laptop and you can install the OS onto the disk. Here I have an issue where I boot from USB but have access to USB only but not to ssd disk. Does that make more sense now? I am afraid this is actually Windows question not linux/unraid related, as once you boot into pxe you are effectively inside WDS environment. I am looking for a command that I could somehow mount/append that virtual disk of VM2 (.img file). Quite frankly I don't even know if this is even possible.
March 5, 20224 yr 23 minutes ago, Januszmirek said: Does that make more sense now? Yes, just a couple of more questions.. I understood you don't want to go with bare metal, I asked about it just to understand the workflow. So, case 1 with bare metal, you have a wds server machine and another machine with windows 10, connected over a network, each machine has its own hd with its operating system. You boot from the windows 10 machine over pxe network to the wds server, and from there in some way you are able to see the hd of the windows 10 machine and do your things. In case 2, with 2 vms (one wds server and one windows 10), you run both vms at the same time, both are connected within the same network, you boot the win10 vm over pxe successfully to the wds server vm, but the hd (img) of the windows 10 vm is not there, am I right? If this is the case, can you attach the xml of the 2 vms, especially that of the win10 client? I suspect the issue is that you have your hd in the win 10 vm (img file) attached to a virtio controller and changing it to sata may solve your issue, if you attach the xml I can modify it. Edited March 5, 20224 yr by ghost82
March 5, 20224 yr 20 minutes ago, ghost82 said: So, case 1 with bare metal, you have a wds server machine and another machine with windows 10, connected over a network, each machine has its own hd with its operating system. You boot from the windows 10 machine over pxe network to the wds server, and from there in some way you are able to see the hd of the windows 10 machine and do your things. 100% correct. 20 minutes ago, ghost82 said: In case 2, with 2 vms (one wds server and one windows 10), you run both vms at the same time, both are connected within the same network, you boot the win10 vm over pxe successfully to the wds server vm, but the hd (img) of the windows 10 vm is not there, am I right? Exactly;) 21 minutes ago, ghost82 said: I suspect the issue is that you have your hd in the win 10 vm (img file) attached to a virtio controller and changing it to sata may solve your issue, if you attach the xml I can modify it. See below;) <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10test1</name> <uuid>c8ab1df9-8dc9-f570-3afc-d40f7e956e84</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="Windows_10b.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='10'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/c8ab1df9-8dc9-f570-3afc-d40f7e956e84_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Dane/Windows/imagetest/Windows 10test1/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <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='0x05' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:d9:d5:39'/> <source bridge='br0'/> <model type='e1000-82545em'/> <boot order='1'/> <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> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain>
March 5, 20224 yr ok, try to change from this: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Dane/Windows/imagetest/Windows 10test1/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> To this: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Dane/Windows/imagetest/Windows 10test1/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk>
March 5, 20224 yr You're a star! It worked. I can see my 'c:\' drive on VM2 and the capturing process is now working fine. Thank you once and again!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.