Re: [libvirt-users] [Qemu-devel] Qcow2
Hello Stefan,
I couldn't find any error when I do consistency check on the image file...
What can be the reason for not starting the VM.
Here I am suspecting when the base server go for reboot lesser image will start and it
cached and larger image will take more time to create the cache...
Was this correct... if yes could you please help me how to increase the caching...
Thanks,
-Arun
-----Original Message-----
From: Stefan Hajnoczi [mailto:stefanha@gmail.com]
Sent: Thursday, May 19, 2011 1:53 PM
To: Arun Sasi V (WI01 - Manage IT)
Cc: stefanha(a)linux.vnet.ibm.com; qemu-devel(a)nongnu.org; libvirt-users(a)redhat.com
Subject: Re: [Qemu-devel] Qcow2
On Wed, May 18, 2011 at 7:03 PM, <arun.sasi1(a)wipro.com> wrote:
I was getting only the problem with audio(only Warning and error log)
when I
checking the logs
{snip}
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
HOME=/root USER=root LOGNAME=root TMPDIR=/tmp/root-tmp.2af1b17/files
/usr/bin/kvm -S -M pc -m 512 -smp 4 -name sy0005embinf02 -uuid
9ddfc4b5-51bc-c3e9-3aea-59101bc15174 -monitor pty -pidfile
/var/run/libvirt/qemu//sy0005embinf02.pid -boot c -drive
file=,if=ide,media=cdrom,index=2 -drive
file=/var/lib/libvirt/images/sy0005embinf02.img,if=virtio,index=0,boot=on
-drive file=/var/lib/libvirt/images/sy0005embinf02_vdb.img,if=virtio,index=1
-net nic,macaddr=00:16:36:1d:67:9e,vlan=0,model=virtio -net
tap,fd=23,script=,vlan=0,ifname=vnet2 -serial pty -parallel none -usb -vnc
127.0.0.1:2 -k en-us -soundhw es1370
cont
oss: Could not initialize DAC
oss: Failed to open `/dev/dsp'
oss: Reason: No such file or directory
oss: Could not initialize DAC
oss: Failed to open `/dev/dsp'
oss: Reason: No such file or directory
audio: Failed to create voice `es1370.dac2'
oss: Could not initialize ADC
oss: Failed to open `/dev/dsp'
oss: Reason: No such file or directory
oss: Could not initialize ADC
oss: Failed to open `/dev/dsp'
oss: Reason: No such file or directory
audio: Failed to create voice `es1370.adc'
These audio messages look like warnings, not fatal errors, but I am
not sure. I would view the VM details using virt-manager and remove
the sound card device from the VM if you don't need it.
{snip}
There were no further error messages indicating that starting the VM failed?
When it was not booting up I just given full permission
-rw-r--r-- 1 root root 384M 2010-10-06 08:01 sy0005embinf01.img.gz
-rw-rw-rw- 1 root root 45 2010-10-06 15:43 SLBTemplate.img
-rw-r--r-- 1 root root 45 2010-10-14 11:44 sy0005embapp01.img
-rw-r--r-- 1 root root 412K 2011-01-08 19:54 sy0005embinf02_vdd.img
-rwxrwxrwx 1 root root 609G 2011-05-18 23:41 sy0005embinf02_vdb.img
-rw-rw-rw- 1 root root 41G 2011-05-18 23:51 sy0005embinf02.img
-rw-rw-rw- 1 root root 2.0G 2011-05-18 23:52 sy0005embinf01.img
-rw-rw-rw- 1 root root 3.8G 2011-05-18 23:52 sy0005embldap01.img
Note: it was not working after the full permission too...
Was there any caching problem after the reboot...???
You mentioned using QCOW2. Use "qemu-img check
sy0005embinf02_vdb.img" to run a consistency check on the image file.
There should be no fatal errors.
Stefan