Re: qemu-kvm 0.15 usb problem
I am experiencing the same problem with version 0.15 while 0.14 works flawless. We're using it for an USB ISDN card which freezes the windows host with qemu-kvm 0.15 when "plugged in" while the system is already running or it completely prevents the start of the VM. We experience the same problem with two completely different USB ISDN adapters. I can further debug this problem if necessary. Cheers, Thomas On Wednesday 10 August 2011 09:25:11 Gerd Hoffmann wrote: > On 08/09/11 21:30, Michael wrote: > > Hi All, > > After installed 0.15 ( and 0.15rc1) guest VM failed at some point with > > USB attached with error: > > qemu-system-x86_64: /tmp/qemu-kvm-0.15.0/hw/usb.c:336: > > usb_packet_complete: Assertion `p->owner != ((void *)0)' failed. > > Looks like a bug. > > > host intel,linux-3.0 ( debian squeeze x64 ) > > start with "qemu-system-x86_64 -m 512 -smp 2 /BIG/Virtual/debian6.base > > -usb -usbdevice host:067b:2303" > > What kind of device is this? > > cheers, >Gerd > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: qemu-kvm 0.15 usb problem
Hi Gerd, I tried with the branch you suggested but it didn't work either. The whole WinXP VM crashed once I virtually "plugged in" the USB ISDN card. I also tried the qemu-kvm-15.1 release but that also didn't work. Do you have any further suggestions? How can I assist in debugging that problem? Cheers Thomas On Monday 19 September 2011 08:30:11 Gerd Hoffmann wrote: > On 09/16/11 18:22, Thomas Beinicke wrote: > > I am experiencing the same problem with version 0.15 while 0.14 works > > flawless. > > We're using it for an USB ISDN card which freezes the windows host with > > qemu-kvm 0.15 when "plugged in" while the system is already running or it > > completely prevents the start of the VM. > > We experience the same problem with two completely different USB ISDN > > adapters. > > > > I can further debug this problem if necessary. > > Try http://www.kraxel.org/cgit/qemu/log/?h=usb.25.stable > > cheers, >Gerd > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
High CPU load on target host after migration
Hi, I have been toying around with kvm / libvirt / virt-manager and it's migration feature. Both host machines are running a 2.6.33 Kernel. One host is a Dual Quad Core Intel Xeon E5520 @ 2.27GHz and the other is a Dual Quad Core Intel E5420 @ 2.50GHz. Migrating Linux machines works great but Windows XP SP3 is giving me a headache. The migration process finishes without any crash/error but the CPU load on the target host is ~50% on two cores. There is no CPU intensive task running inside the VM though. "Removing" the network card from the VM and migrating it between the two machines doesn't seem to trigger the high CPU load. As network driver I tried the realtek and Red Hat virtio driver but it doesn't seem to make a difference. Any insights on what could cause this situation and how to best debug it? Cheers, Thomas -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: High CPU load on target host after migration
I forgot to mention that I am using qemu-kvm-0.12.3 on all of my machines. I am also using bridged networking on all hosts. Is anyone else on the list doing life migration and is facing the same problems I mentioned below? I would really like to debug this further but I need some assistance on how to proceed. Thanks, Thomas On Wednesday 28 April 2010 23:14:40 you wrote: > Hi, > > I have been toying around with kvm / libvirt / virt-manager and it's > migration feature. > Both host machines are running a 2.6.33 Kernel. > > One host is a Dual Quad Core Intel Xeon E5520 @ 2.27GHz and the other is a > Dual Quad Core Intel E5420 @ 2.50GHz. > > Migrating Linux machines works great but Windows XP SP3 is giving me a > headache. > The migration process finishes without any crash/error but the CPU load on > the target host is ~50% on two cores. There is no CPU intensive task > running inside the VM though. > "Removing" the network card from the VM and migrating it between the two > machines doesn't seem to trigger the high CPU load. > As network driver I tried the realtek and Red Hat virtio driver but it > doesn't seem to make a difference. > > Any insights on what could cause this situation and how to best debug it? > > Cheers, > > Thomas > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
On Wednesday 10 February 2010 09:30:57 xming wrote: > hi, Hi, > I am hitting this bug as well, using qemu-kvm-0.12.2 with the following > command > > /usr/bin/kvm -name pfsense,process=pfsense -m 256 -vnc > 192.168.0.254:13 -smp 1 -hda /dev/volume01/G-pfsense -vga std > Option 'ipv4': Use 'on' or 'off' > Failed to parse "yes" for "dummy.ipv4" > inet_listen_opts: bind(ipv4,192.168.0.254,5913): Address already in use > inet_listen_opts: FAILED It looks like the same VNC port (5913 in your case) is already in use by another VM or service. Does 'netstat -lnp' list any program using that port? For me the first two messages disappeard when I left out the IP in the vnc defintion. So instead of -vnc 192.168.0.254:13 I just used -vnc :13 . Of course that makes only sense if you just have a single IP on that machine and there is no need to bind it to a specific one. Cheers, Thomas > > I check the source in the tarball and git master, this patch is not in > them. Is there any reason that this is not merged? > > cheers > > > PS. this mail was only sent to Marcelo the first time, sorry for that. > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: How to convert a physical drive (running Vista) as VM to be run on KVM
On Tuesday 16 February 2010 07:39:50 sati...@pacific.net.hk wrote: > Hi folks, Hi, > Host - Fedora 12 64bit > Windows Vista 32bit - running another drive > KVM > > > $ sudo fdisk -l > Disk /dev/sda: 1000.2 GB, 1000204886016 bytes > 255 heads, 63 sectors/track, 121601 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x0003a4bf > > Device Boot Start End Blocks Id System > /dev/sda1 * 1 26 204800 83 Linux > Partition 1 does not end on cylinder boundary. > /dev/sda2 26 121601 976555201 8e Linux LVM > > Disk /dev/sdb: 40.0 GB, 40027029504 bytes > 255 heads, 63 sectors/track, 4866 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x0883bef2 > > Device Boot Start End Blocks Id System > /dev/sdb1 * 14867390860807 HPFS/NTFS > > Disk /dev/dm-0: 989.7 GB, 989704749056 bytes > 255 heads, 63 sectors/track, 120324 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x > > Disk /dev/dm-0 doesn't contain a valid partition table > > Disk /dev/dm-1: 10.3 GB, 10284433408 bytes > 255 heads, 63 sectors/track, 1250 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x > > Disk /dev/dm-1 doesn't contain a valid partition table > > - end - > > > I have created; > > $ sudo dd if=/dev/sdb of=/home/satimis/VM/VMWIN/vm07_vista.qcow2 > 78177792+0 records in > 78177792+0 records out > 40027029504 bytes (40 GB) copied, 1160.35 s, 34.5 MB/s When you "dd" off a device it will always be raw format, kvm will recognize it as raw even though the extension is qcow2. If you really want a qcow container you have to convert it with "qemu-img". > > I haven't figured out what options will be up on running; > > qemu /home/satimis/VM/VMWIN/vm07_vista.qcow2 > > -m 1024 ? > -soundhw all ? man qemu gives you all the available options. There are also a lot of examples on google and on this mailing list. > etc. > > > Will /etc/libvirt/qemu/vm07_vista.xml be created automatically running > above command? For hard drives you should use something like this: -drive file=hda.qcow2,boot=on Again, check the manpage for more details on drive options. Cheers, Thomas > Please shed me some light. Pointer would be appreciated. TIA > > > B.R. > Stephen L > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 0.12.x: message "Option 'ipv4': Use 'on' or 'off'"
I get the same message since the update, is it -chardev option related? On Saturday 02 January 2010 11:53:42 Thomas Mueller wrote: > hi > > since 0.12.x i get the following messages starting a vm: > > Option 'ipv4': Use 'on' or 'off' > Failed to parse "yes" for "dummy.ipv4" > > > command is: > > > kvm -usbdevice tablet -drive file=~/virt/xp/drive1.qcow2,cache=writeback - > drive file=~/virt/xp/drive2.qcow2,cache=writeback -net nic -net > user,hostfwd=tcp:127.0.0.1:3389-:3389 -k de-ch -m 1024 -smp 2 -vnc > 127.0.0.1:20 -monitor unix:/var/run/kvm-winxp.socket,server,nowait - > daemonize -localtime > > what is option ipv4? > > - Thomas > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Migration VMWare Server -> KVM
Hi all, I am trying to migrate lots of VMWare server VMs to KVM. The linux machines are not much of a problem but the windows machines cause me some headaches. Does anyone has experience in with the migration process? As soon as I try to boot it I get a bluescreen (probably related to the block IO driver used). AFAIK VMware uses an LSI Logic driver in their VMs. I have tried with "if=scsi" as well as IDE. Anyone has any howto or hints on how to accomplish that or am I totally wasting my time? regards, Thomas -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Migration VMWare Server -> KVM
On Tuesday 12 January 2010 17:36:49 you wrote: > Hi! > On Tue, 2010-01-12 at 17:20 +0100, Thomas Beinicke wrote: > > > Hi all, > > I am trying to migrate lots of VMWare server VMs to KVM. The linux machines > are not much of a problem but the windows machines cause me some headaches. > > Does anyone has experience in with the migration process? As soon as I try > to boot it I get a bluescreen (probably related to the block IO driver > used). > > > > Look into http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE > Thanks, that guide was very helpful. I managed to migrate 3 Windows XP SP3 machines today. I also installed the Red Hat virtio net drivers which work like a charm as well. The only downside was that I had to activate Windows again since the hardware has "changed" :) Cheers, Thomas > They have some very good hints and a reg file that allows you to use IDE > drivers for the migration. > > > Best regards > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: repeatable hang with loop mount and heavy IO in guest
On Thursday 21 January 2010 21:08:38 RW wrote: > Some months ago I also thought elevator=noop should be a good idea. > But it isn't. It works good as long as you only do short IO requests. > Try using deadline in host and guest. > > Robert @Robert: I've been using noop on all of my KVMs and didn't have any problems so far, never had any crash too. Do you have any performance data or comparisons between noop and deadline io schedulers? Cheers, Thomas -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
