virt December 2011

virt@lists.centos.org

11 participants
15 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt December 2011