virt December 2011

virt@lists.centos.org

11 participants
15 discussions

Has anyone been able to start a Fedora 16 VM in Xen PV?
by Scot P. Floess 08 Jul '12

08 Jul '12

All, I've had a heck of a time getting Fedora 16 to run as a guest VM under CentOS 5.7 host as a paravirtualized Xen guest. I believe the issue has something to do with Fedora 16 using grub2... When I attempt to start the VM (via xm create), I get this error: Using config file "/etc/xen/fedora-workstation". Traceback (most recent call last): File "/usr/bin/pygrub", line 686, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger "xend" Error: Boot loader didn't return any data! In my kickstart, I had to create a partition for F16 as: part biosboot --fstype=biosboot --size=1 I didn't readily find the error when googling... Has anyone been able to run F16 as a PV guest? And if so, what did you do to make it happen????? Thanks!!!!!!!!!!!!! Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare

6 10

centos6 and xen4 dom0 memory allocation
by Peter Peltonen 08 Jul '12

08 Jul '12

Hi, This is slightly OT as xen is not officially supported in EL6. But maybe someone else is running it on centos6 as well and could help me out here: I have problems allocating a static amount of memory for my xen dom0. It seems to reduce when new domUs are created, even though I *think* ballooning is disabled. Can someone advise me what I'm doing wrong? I have xen-4.1.1-3 installed from http://xenbits.xen.org/people/mayoung/EL6.xen on my centos6 server. I am running 2.6.32-131.12.1.el6.xendom0.x86_64 kernel available from the same place. 'xl info' reports about available memory as follows: total_memory : 24567 free_memory : 3698 xen_commandline : dom0_mem=2048M and in xend-config.sxp I have: (dom0-min-mem 256) (enable-dom0-ballooning no) (total_available_memory 0) Now one would think that I should have 2048M memory for dom0, right? I started from there, but when starting domUs it has been reduced to 1140M even though I think ballooning is disabled and there is free memory available? And the weird thing is that dom0 has done some swapping: # free -mt total used free shared buffers cached Mem: 1140 1052 88 0 2 12 -/+ buffers/cache: 1038 102 Swap: 8194 85 8109 Total: 9335 1138 8197 Shutting down domUs and making more memory available does not reverse the effect, dom0 does not allocate more memory. What am I missing here or is my xen setup acting strangely here? Best regards, Peter

2 4

qemu-kvm
by Radek Bursztynowski 06 Jan '12

06 Jan '12

Hi everybody, I am new member at this list but I am not new with CentOS. I use CentOS 5.x till today, but I try CentOS 6.2 now. Regarding virtualization on CentOS 6.2 (i386) I have some problem. I installed all rpm packages joined to CentOS 6.2 and virtualization. When I try to start virt-manager I receive request to install qemu-kvm package. I try to do it accepting virt-manager advice but i can read message that this package is not available. So, I try to install qemu-kvm using yum - still nothing. Next I added additional packages and repositories as follow: epel-release-6-5.noarch.rpm remi-release-6.rpm centos-release-cr-6-0.el6.centos.i686.rpm rpmfusion-free-release-6-0.1.noarch.rpm rpmfusion-nonfree-release-6-0.1.noarch.rpm Still nothing. I visited http://rpmfind.net/linux/rpm2html/search.php?query=qemu-kvm but there are qemu-kvm packages destined for CentOS x86_64. Could anybody advice me where qemu-kvm packages for CentOS 6.2 i386 is placed or what should I to do to fix my problem? Thanks for any help, Radek

4 7

Pass iPhone/iTouch through kvm to Win7 VM?
by David McGuffey 30 Dec '11

30 Dec '11

Started this over on the main list, but remembered there is a CentOS-virt list also where this would be more appropriate. At home, I'm all Linux and only run Windows in VMs when I absolutely have to (e.g., TurboTax on Win7 during the tax filing season). Now I'm trying to get Win7 running in a VM on CentOS 5.6 and kvm to connect to my iTouch and iPhone so I can sync them with iTunes. When I plug the iPhone in and run lsusb I get an address of 05AC:12A0 Bus 006 Device 001: ID 0000:0000 Bus 007 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 011: ID 05ac:12a0 Apple, Inc. Bus 001 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 I put that into a hostdev block in the xml file that defines the VM. <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x05AC'/> <product id='0x12A0'/> </source> </hostdev> But...no joy. Win7 works in all other aspects...just won't connect to a usb device. Anyone get kvm to pass an iTouch or iPhone through to the VM so it can communicate with iTunes? I'm thinking this may be a permissions and SELinux issue...the usb device is owned by 'dave' (my CentOS login id), but the VM is owned by kvm (different owner and different SELinux context). I remember reading a lengthy discussion on how to get kvm to run as as a regular user...will have to go find it. Once I clean the host up and back up some data, I'll be migrating to CentOS 6.2. Does that version have more capability to deal with usb pass-through? Dave

1 1

time drift with kvm guest
by thomas veymont 23 Dec '11

23 Dec '11

hello, a big time drift appears along time on a guest VM (time is going too slow on the guest). here the setup: ~ physical machine ~ Centos 6.0 x86_64 time set with ntpd Intel(R) Xeon(R) CPU X5650 /proc/cpuinfo shows the "constant_tsc" bit. ~ guest OS ~ Centos 6.0 x86_64 /proc/cpuinfo : processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : QEMU Virtual CPU version (cpu64-rhel6) stepping : 3 cpu MHz : 2666.998 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm up rep_good unfair_spinlock pni cx16 hypervisor lahf_lm bogomips : 5333.99 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual at boot time : [root@xxxx ~]# dmesg | egrep -i 'clock|tsc|time' kvm-clock: Using msrs 12 and 11 kvm-clock: cpu 0, msr 0:18c1901, boot clock ACPI: PM-Timer IO Port: 0xb008 kvm-clock: cpu 0, msr 0:1e16901, primary cpu clock ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Switching to clocksource kvm-clock uhci_hcd 0000:00:01.2: setting latency timer to 64 rtc_cmos 00:01: setting system clock to 2011-12-15 09:33:28 UTC (1323941608) ata_piix 0000:00:01.1: setting latency timer to 64 Clocksource tsc unstable (delta = -547592984 ns) [root@xxxx ~]# cat /sys/devices/system/clocksource/clocksource0/available_clocksource kvm-clock acpi_pm [root@xxxx ~]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock cpuspeed service is not active on the guest. acpid service is active on the guest (so it can be shut down from the host with "virsh shutdown"). reading Redhat documentation, I did everything ok (that is : guest clocksource set to "kvm-clock" and physical host has a CPU with constant_tsc flag + time set with NTP) : http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualiz… is that right ? does anyone have a suggestion about this problem ? thanks Tom

1 0

Confusion over steps to add new logical volume to guest VM
by Jeff Boyce 21 Dec '11

21 Dec '11

Greetings - I am hoping someone can confirm for me the steps that I am using to add an LV to an existing Guest in KVM, and what I am seeing as I do some of these steps. My host (earth) is CentOS 6 and so is my guest (disect). The guest (disect) is my testing server. The main objective of what I am trying to do is add a logical volume for /var into my guest. The LV (lv_disectvar) is part of an existing VG (vg_mei) on the host. When I installed my guest OS, I could only select one LV from my host for the installation, so the entire OS was installed into lv_disectroot. I have added lv_disectvar into the storage pool available for VMs through the VirtManager GUI, and successfully added the lv_disectvar to the guest VM also through the VirtManager GUI. And now I want to move my /var over to the new LV. My notes show that I created the LV about two weeks ago, and added it to the guest VM last week. I don't see any other notes indicating that I did anything else with this LV. Today I finally got around to the task of moving /var from lv_disectroot over to lv_disectvar and editing fstab so that it would automount at boot. So here are the steps that I was going to do, and what I saw that made me pause. 1. Verify that the device is identified by the guest, and get the UUID for fstab. [jeffb@disect ~]$ ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx. 1 root root 10 Dec 12 14:37 738923a4-c345-40bf-a850-4454caa152b6 -> ../../vda2 lrwxrwxrwx. 1 root root 9 Dec 12 14:37 db1230fb-a061-4ea4-9229-c5953d29aef8 -> ../../vdb <----lv_disectvar lrwxrwxrwx. 1 root root 10 Dec 12 14:37 db70a6db-3640-4392-b9ba-49839d6e4b45 -> ../../vda1 2. Create a mount point for /dev/vdb [root@disect jeffb]# mkdir /mnt/var 3. Mount the device [root@disect jeffb]# mount -t ext4 /dev/vdb /mnt/var 4. At this point I was going to move /var to /mnt/var but decided to check the mount first [root@disect mnt]# cd /mnt/var [root@disect var]# ls cache lib lock log lost+found run 5. When I saw the directories listed I was initially confused and thought I had possibly mounted the wrong device. But after double checking everything it appears I did not do anything wrong. As I mentioned above my notes do not show that I did anything with this LV other than create it and attach it to the guest VM. I am wondering about the source of these directories and all the subsequent files under them. My assumption is that these were created during the creation of the LVM and are part of its file system. Is that a correct assumption? How could I confirm this assumption? 6. Can I just add a /var directory to this and move my /var from /vda2 over to /vdb? 7. Then I would add the following line to my /etc/fstab in the guest disect UUID=db1230fb-a061-4ea4-9229-c5953d29aef8 /var ext4 defaults 1 2 8. I initially tried just adding the above line to my fstab, but realized after the guest VM hung on rebooting that /var is already mounted under /, and that of course caused a problem when booting. Thanks for any advice you can provide. Jeff Boyce Meridian Environmental www.meridianenv.com

2 2

Re: [CentOS-virt] New Guess OS Creation Problem
by takizo 12 Dec '11

12 Dec '11

On Dec 12, 2011, at 11:33 PM, Stefan Hajnoczi wrote: > On Mon, Dec 12, 2011 at 3:19 PM, takizo <paulooi(a)takizo.com> wrote: >> >> On Dec 12, 2011, at 11:08 PM, Stefan Hajnoczi wrote: >> >>> On Mon, Dec 12, 2011 at 2:50 PM, takizo <paulooi(a)takizo.com> wrote: >>>> >>>> On Dec 12, 2011, at 6:56 PM, Stefan Hajnoczi wrote: >>>> >>>>> On Sun, Dec 11, 2011 at 4:40 PM, takizo <paulooi(a)takizo.com> wrote: >>>>>> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name database -uuid f3e9f320-7826-7e50-94bb-1833f7fd9dfb -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/database.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -drive file=/opt/cibai/database,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/opt/ISO-Download/FreeBSD-8.2-RELEASE-amd64-disc1.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,aio=threads -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=22,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:77:a5:a6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:2,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 >>>>>> char device redirected to /dev/pts/6 >>>>>> Using CPU model "cpu64-rhel6" >>>>>> >>>>>> block I/O error in device 'drive-ide0-0-0': Invalid argument (22) >>>>> >>>>> Is /opt/cibai/database on a special filesystem or exotic storage setup? >>>>> >>>>> Please check dmesg on the host for any kernel messages regarding I/O errors. >>>>> >>>>> Please try reading the file on the host to check whether the I/O error >>>>> is happening on the host and not related to KVM: >>>>> >>>>> $ dd if=/opt/cibai/database of=/dev/null iflag=direct >>>>> >>>>> Stefan >>>> >>>> Hi Stefan, >>>> >>>> When I quit the installation, further see the error messages >>>> >>>> ide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pending2011-12-12 22:47:51.427: shutting down >>>> >> >> Hi Stefan >> >>> Okay, so if I understand correctly you have CentOS 6.1 host running >>> FreeBSD and CentOS guest installs to emulated IDE drives. You're >>> getting failed I/O requests with EINVAL (22). You have verified that >>> dd if=/opt/vm/database.img of=/dev/null iflag=direct reads the image >>> file without errors. >> >> That is right, both also emulated on IDE drive >> >>> >>> Can you please try the CentOS guest install with a virtio-blk drive >>> instead of IDE? This should show whether this problem is related to >>> IDE or a general issue in how QEMU accesses the host file. >> >> Took your advice installed Centos on VirtIO drive and it's ok. >> >> Does it means it's IDE problem on the OS itself? > > The physical drive in your machine is probably fine. QEMU emulates an > IDE controller and disks for the guest. It looks like there is a bug > in the IDE emulation code inside QEMU which leads to these errors. I suspect the problem might came from QEMU, because day before it was working before before I upgrade to latest QEMU. > > In general virtio-blk is the recommended storage interface because it > delivers better performance. I'm not up-to-speed on how stable the > FreeBSD virtio drivers are but I think they are available if you > search. Unfortunately I am running FreeBSD 8.2, it's not natively supported yet. I guess now interim solutions will be duplicate from some current running VM. > >> 2011-12-12 23:15:06.759: starting up >> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name centos -uuid 0752c74e-1d51-d529-f66f-8df9a28670ed -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/centos.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -drive file=/opt/vm/centos.img,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=threads -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/opt/ISO-Download/CentOS-6.0-x86_64-minimal.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,aio=threads -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:10:bc:5d,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:3,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 >> char device redirected to /dev/pts/9 >> Using CPU model "cpu64-rhel6" > > At this stage of debugging I would try enabling SystemTap probes in > QEMU related to block I/O. This produces a detailed log of what is > happening inside QEMU. > > strace -f -p $PID_OF_QEMU might also reveal how the I/O is failing. > > Finally, gdb could be of use. > > I'm not sure how familiar or easy it is for you to try these so let's > see if Kevin or someone else has other ideas before getting into the > nitty-gritty of finding out why you get EINVAL (22). I will see what I can grab and share in the list. Thanks Stefan > > Stefan

1 0

Re: [CentOS-virt] New Guess OS Creation Problem
by takizo 12 Dec '11

12 Dec '11

On Dec 12, 2011, at 11:08 PM, Stefan Hajnoczi wrote: > On Mon, Dec 12, 2011 at 2:50 PM, takizo <paulooi(a)takizo.com> wrote: >> >> On Dec 12, 2011, at 6:56 PM, Stefan Hajnoczi wrote: >> >>> On Sun, Dec 11, 2011 at 4:40 PM, takizo <paulooi(a)takizo.com> wrote: >>>> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name database -uuid f3e9f320-7826-7e50-94bb-1833f7fd9dfb -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/database.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -drive file=/opt/cibai/database,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/opt/ISO-Download/FreeBSD-8.2-RELEASE-amd64-disc1.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,aio=threads -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=22,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:77:a5:a6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:2,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 >>>> char device redirected to /dev/pts/6 >>>> Using CPU model "cpu64-rhel6" >>>> >>>> block I/O error in device 'drive-ide0-0-0': Invalid argument (22) >>> >>> Is /opt/cibai/database on a special filesystem or exotic storage setup? >>> >>> Please check dmesg on the host for any kernel messages regarding I/O errors. >>> >>> Please try reading the file on the host to check whether the I/O error >>> is happening on the host and not related to KVM: >>> >>> $ dd if=/opt/cibai/database of=/dev/null iflag=direct >>> >>> Stefan >> >> Hi Stefan, >> >> When I quit the installation, further see the error messages >> >> ide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pendingide_dma_cancel: aiocb still pendingide_dma_cancel: BM_STATUS_DMAING still pending2011-12-12 22:47:51.427: shutting down >> Hi Stefan > Okay, so if I understand correctly you have CentOS 6.1 host running > FreeBSD and CentOS guest installs to emulated IDE drives. You're > getting failed I/O requests with EINVAL (22). You have verified that > dd if=/opt/vm/database.img of=/dev/null iflag=direct reads the image > file without errors. That is right, both also emulated on IDE drive > > Can you please try the CentOS guest install with a virtio-blk drive > instead of IDE? This should show whether this problem is related to > IDE or a general issue in how QEMU accesses the host file. Took your advice installed Centos on VirtIO drive and it's ok. Does it means it's IDE problem on the OS itself? 2011-12-12 23:15:06.759: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name centos -uuid 0752c74e-1d51-d529-f66f-8df9a28670ed -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/centos.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -drive file=/opt/vm/centos.img,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=threads -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/opt/ISO-Download/CentOS-6.0-x86_64-minimal.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,aio=threads -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:10:bc:5d,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:3,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 char device redirected to /dev/pts/9 Using CPU model "cpu64-rhel6" > > Stefan

1 0

Re: [CentOS-virt] New Guess OS Creation Problem
by takizo 12 Dec '11

12 Dec '11

1 0

Re: [CentOS-virt] New Guess OS Creation Problem
by takizo 12 Dec '11

12 Dec '11

1 0

Re: [CentOS-virt] New Guess OS Creation Problem
by takizo 12 Dec '11

12 Dec '11

On Dec 12, 2011, at 6:56 PM, Stefan Hajnoczi wrote: > On Sun, Dec 11, 2011 at 4:40 PM, takizo <paulooi(a)takizo.com> wrote: >> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name database -uuid f3e9f320-7826-7e50-94bb-1833f7fd9dfb -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/database.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -drive file=/opt/cibai/database,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/opt/ISO-Download/FreeBSD-8.2-RELEASE-amd64-disc1.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,aio=threads -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=22,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:77:a5:a6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:2,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 >> char device redirected to /dev/pts/6 >> Using CPU model "cpu64-rhel6" >> >> block I/O error in device 'drive-ide0-0-0': Invalid argument (22) > Hi Stefan, Thanks for responding. > Is /opt/cibai/database on a special filesystem or exotic storage setup? It's an direct attached disk. /dev/sdb1 134G 30G 98G 23% /opt > > Please check dmesg on the host for any kernel messages regarding I/O errors. I have checked dmesg, /var/log/messages and the one I pasted was from KVM storage. Not much error I can see > > Please try reading the file on the host to check whether the I/O error > is happening on the host and not related to KVM: > > $ dd if=/opt/cibai/database of=/dev/null iflag=direct I have read the files. The file seems ok. dd if=/opt/vm/database.img of=/dev/null iflag=direct 52428800+0 records in52428800+0 records out 26843545600 bytes (27 GB) copied, 70.3967 s, 381 MB/s I tried the installation again, same problem giving me IO error. Is there any other to show more verbose logging? 2011-12-12 22:40:33.625: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name database -uuid 8490fea3-cb30-4ac5-2779-3681a77e7b03 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/database.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -drive file=/opt/vm/database.img,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/opt/ISO-Download/FreeBSD-8.2-RELEASE-amd64-disc1.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,aio=threads -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=22,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:c8:1c:b9,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:3,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 char device redirected to /dev/pts/7 Using CPU model "cpu64-rhel6" block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) > > Stefan

1 0

New Guess OS Creation Problem
by takizo 11 Dec '11

11 Dec '11

Hi All, I am running on CentOS Released 6.1 final. Been using and running Linux KVM quite well for quite some time, something goes wrong after I perform yum upgrade. I created new VM yesterday without any problem, same exact installation procedure, installed FreeBSD 8.2. I tried to create a new VM today after yum upgrade, it's able to detect the hard disk, when I start commit FreeBSD 8.2 installation, it complains cannot write to disk as stated the error message below. block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) Below is the log I capture from the VM log file -- Log start -- 2011-12-12 00:23:39.485: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name database -uuid f3e9f320-7826-7e50-94bb-1833f7fd9dfb -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/database.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -drive file=/opt/cibai/database,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/opt/ISO-Download/FreeBSD-8.2-RELEASE-amd64-disc1.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,aio=threads -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=22,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:77:a5:a6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:2,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 char device redirected to /dev/pts/6 Using CPU model "cpu64-rhel6" block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) -- Log End -- Below is the software version currently running; gpxe-roms-qemu-0.9.7-6.7.el6.noarch qemu-img-0.12.1.2-2.160.el6_1.8.x86_64 qemu-kvm-0.12.1.2-2.160.el6_1.8.x86_64 libvirt-client-0.8.7-18.el6_1.4.x86_64 libvirt-python-0.8.7-18.el6_1.4.x86_64 libvirt-0.8.7-18.el6_1.4.x86_64 Any of you having the problem as well? I am planning to install CentOS as guest and see whether is has the same problem as well. Thanks. -- Paul Ooi

1 0

Selecting raw logical volumes during guest VM creation
by Jeff Boyce 08 Dec '11

08 Dec '11

Greetings - I have stepped through the first guest OS installation (a testing VM) on my new server and have a technical question that I hope someone might be able to help me with. I have exhausted my google search ability and have not been able to find the details I am looking for. In general the question I am trying to answer is how to select and use multiple raw logical volumes when creating a new VM, rather than just a single raw logical volume (if it is possible). Here are the details... I have setup my hardware with a single volume group (vg_mei) encompassing my entire raid array. With this I set up my base OS (CentOS 6) for the purpose of managing the hardware and the few VMs that will be created (using KVM). Three LVs were created for the base OS (lv_hostroot, lv_hostswap, and lv_hostvar) to contain the appropriate parts of the base OS file system. As expected, /boot was located outside the volume group. In preparation for installing my testing VM, I created two more LVs (lv_testroot and lv_testvar) to contain the appropriate parts of the guest file system. Following the RHEL6 Virtualization Guide (Section 25.1.4 for using LVM-based Storage Pools) I successfully added all the logical volumes that had been created into the host storage pool. So when I start the Virt-Manager GUI and work through the five steps for creating a new VM (shown in Section 6.3 of the RHEL6 Virtualization Guide), Step #4 provides the option for creating or using existing storage for the VM. When I select the option to use "managed or other existing storage" then choose the browse button, I am given a dialog box that displays all LVs that I have previously created. At this point though I am only allowed to select a single LV to install the guest OS. So I chose the lv_testroot logical volume and the installation was able to be completed (there was a little manual intervention required during the OS installation partitioning layout in order to prevent nesting LVMs). But I am wondering if there is a way during Step #4 of the VM creation to pass multiple LVs to the system so that during the OS installation process you have all the LVs that you want for the partitioning layout. I assume that there is a way to add an LV to an existing VM after the guest OS is installed, then move portions of the file system over to the added LV. Following my example above, adding lv_testvar to the testing VM then move my /var directory over and add an entry in fstab to mount it at boot time. I am doing some google searching right now to try and verify the details on how to do this. I curious about the best way to do the VM setup since I will be creating a new VM for my Samba file server, which will also include the users home directories. So for the Samba VM I will create in advance LVs for /, /var, /home, and /sambashare. Also is it possible to likewise add an LV for /swap after the fact (or is it really needed anymore for something like a small file server)? I want to use raw LVs from my host system in order to be able to use the full capabilities of LVM for each of my guest VMs. I realize that this may create a number of LVs to manage, but I don't expect to have more than 4 VMs on this box and I have worked out a good naming scheme for the LVs in order to keep track of everything. Any technical help, or pointers to blogs or technical documents that I may have missed, is greatly appreciated. Thanks. Jeff Boyce Meridian Environmental www.meridianenv.com

2 1

How to add additional Serial Ports to a KVM guest?
by James B. Byrne 01 Dec '11

01 Dec '11

The vm host shows this: # setserial -g /dev/ttyS* /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 /dev/ttyS1, UART: 16950/954, Port: 0xd040, IRQ: 17 /dev/ttyS2, UART: 16950/954, Port: 0xd048, IRQ: 17 /dev/ttyS3, UART: 16950/954, Port: 0xd050, IRQ: 17 # # ll /dev/ttyS* crw-rw----. 1 root dialout 4, 64 Nov 10 12:18 /dev/ttyS0 crw-rw----. 1 root dialout 4, 65 Nov 10 12:18 /dev/ttyS1 crw-rw----. 1 root dialout 4, 66 Nov 10 12:18 /dev/ttyS2 crw-rw----. 1 root dialout 4, 67 Nov 10 12:18 /dev/ttyS3 By default serial 0 o guests is assigned to pty and has a device path of '-'. I have installed on the host a 4-port serial card, as evidenced above. When I add the first additional port to the guest (serial 1) and use '/dev/ttyS1' as the path the guest will boot. However, if I add a second serial port (serial 2) using path '/dev/ttyS2' then I get this error and the guest will not start: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 878, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1313, in startup self._backend.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/1 isa irq 4 already assigned How does one configure additional serial ports on a kvm guest? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

VM fails to start on host bootup, but starts fine manually. Why?
by Aleksey Tsalolikhin 01 Dec '11

01 Dec '11

I have 5 VMs on my host. The first four are setup to start on boot. But only the first three end up running. The fourth has to be started manually. "Start virtual machine on host bootup" is checked on all four VMs but the fourth VM does not get started on host bootup. After the host boots up, the VM is "Shutdown" state. If I go into "virt-manager" and click "Run", it starts just fine. I looked in /var/log/xen/ and did not see anything related, but I don't know what I'm looking for. Any suggestions? Best, -at

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt December 2011