Am Samstag 08 Januar 2011 schrieben Sie:
Hi,
I want to migrate from vmware to KVM. Therefore I have installed debian
stable (lenny) and create two virtual machines (KVM).
Both (XP as well as Vista) running fine.
After upgrading to debian testing (sqeeze) both XP-guest as well as
Vista-guest didn't start anymore.
Both are failing during preparation, probably because of a
network-problem.
I will give XP as an example:
cat /var/log/libvirt/qemu/devel-xp.log.2
/usr/bin/kvm -S -M pc -m 256 -smp 1 -name devel-xp -monitor
pty -localtime -no-acpi -boot c -drive
file=/KVM-Images/devel-xp.qcow2,if=ide,index=0,boot=on -drive
file=/mnt/MultiMedia/CD-Server/Betriebssysteme/Windows/WindowsNT/WindowsXPpro_sp2_de.iso,if=ide,media=cdrom,index=2
-net
nic,macaddr=54:52:00:29:1a:2d,vlan=0 -net
tap,fd=11,script=,vlan=0,ifname=vnet0 -serial pty -parallel
none -usb -usbdevice tablet -vnc 127.0.0.1:0 -k de
char device redirected to /dev/pts/1
char device redirected to /dev/pts/2
info cpus
-> the above will run fine before the upgrade
the following will fail after the upgrade
tail /var/log/messages:
Jan 8 00:56:33 linux-dev libvirtd: 00:56:33.461: warning :
qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably
failed
Jan 8 00:56:33 linux-dev kernel: [ 1903.710664] device vnet0 entered
promiscuous mode
Jan 8 00:56:33 linux-dev kernel: [ 1903.711011] br0: port 2(vnet0)
entering
learning state
Jan 8 00:56:33 linux-dev kernel: [ 1904.022502] br0: port 2(vnet0)
entering
disabled state
Jan 8 00:56:33 linux-dev kernel: [ 1904.024752] device vnet0 left
promiscuous mode
Jan 8 00:56:33 linux-dev kernel: [ 1904.024752] br0: port 2(vnet0)
entering
disabled state
tail -f /var/log/libvirt/qemu/devel-xp.log
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
HOME=/ QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m
512 -smp 1,sockets=1,cores=1,threads=1 -name devel-xp -uuid
1b412c63-dcc0-739f-3c27-630147e6b162 -nodefaults -chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/devel-xp.monitor,server,nowait -mon
chardev=monitor,mode=readline -rtc base=localtime -no-acpi -boot c
-drive
file=/KVM-Images/devel-xp.qcow2,if=none,id=drive-ide0-0-0,boot=on,format=raw
-device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive
file=/mnt/MultiMedia/CD-Server/Betriebssysteme/Windows/WindowsNT/WindowsXPpro_sp2_de.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw
-device
ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -device
rtl8139,vlan=0,id=net0,mac=54:52:00:29:1a:2d,bus=pci.0,addr=0x3 -net
tap,fd=40,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device
isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vnc
127.0.0.1:0 -k de -vga cirrus -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
char device redirected to /dev/pts/4
TUNGETIFF ioctl() failed: Invalid argument
exception 13 (0)
rax 0000000000000010 rbx 0000000000008c00 rcx 0000000000006eb6 rdx
00000000000c8c00
rsi 00000000f2010000 rdi 00000000000c0000 rsp 0000000000006eac rbp
00000000f2010000
r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
0000000000000000
rip 00000000000fde7c rflags 00033002
cs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ds 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
es 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ss 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
fs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0000 (feffd000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt f7910/37
idt f8990/0
cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 --> 00
00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00
00 00 00
Any hints?
Thanks
AthLux
--
Don't Panic
The above problem occurs with Linux kernel "2.6.26-2-686 #1 SMP" but not
with "Linux kernel 2.6.32-5-686 #1 SMP".
At least a workaround for me.
br
AthLux
--
Don't Panic