Using:
kvm-0.12.3
libvirt-0.7.7
kernel-2.6.31
I am trying to persuade my Win XP guest to use the serial which I have
configured using the virt-manager. But whatever I try no COMs appear in
guest. I have tried with socket, tcp, pipe, etc. with just the same
result - no COM within the guest. I have obviously missed something. I
need help to set-up that COM appear and work within guest machine.
guest's XML part for serial looks like:
<serial type='tcp'>
<source mode='connect' host='127.0.0.1' service='4555'/>
<protocol type='raw'/>
<target port='0'/>
</serial>
<console type='tcp'>
<source mode='connect' host='127.0.0.1' service='4555'/>
<protocol type='raw'/>
<target port='0'/>
</console>
Here is the latest command line to run my guest:
/usr/bin/qemu-kvm -S -M pc-0.11 -enable-kvm -m 512 -smp
1,sockets=1,cores=1,threads=1 -name windowsxp -uuid
1f012431-f345-48f4-9ae5-b10787e24de7 -nodefaults -chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/windowsxp.monitor,server,nowait
-mon chardev=monitor,mode=readline -rtc base=localtime -boot c -drive
file=/var/lib/kvm/images/windowsxp/disk0,if=none,id=drive-ide0-0-0,boot=on
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0
-drive if=none,media=cdrom,id=drive-ide0-1-0 -device
ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
file=/var/lib/kvm/images/windowsxp/disk1,if=none,id=drive-ide0-0-1
-device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1
-device rtl8139,vlan=0,id=net0,mac=52:54:00:6b:9d:6e,bus=pci.0,addr=0x4
-net tap,fd=20,vlan=0,name=hostnet0 -device
rtl8139,vlan=1,id=net1,mac=52:54:00:3e:2a:f8,bus=pci.0,addr=0x5 -net
tap,fd=21,vlan=1,name=hostnet1 -device
rtl8139,vlan=2,id=net2,mac=52:54:00:ce:35:fe,bus=pci.0,addr=0x6 -net
tap,fd=22,vlan=2,name=hostnet2 -chardev
socket,id=serial0,host=127.0.0.1,port=4555,server,nowait -device
isa-serial,chardev=serial0 -usb -vnc 127.0.0.1:0 -vga cirrus -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
Iztok
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
