1:03 p.m.
Stefan,
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=o
n -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'
{snip}
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...???
Thanks,
-Arun
-----Original Message-----
From: Stefan Hajnoczi [mailto:stefanha@gmail.com]
Sent: Wednesday, May 18, 2011 10:29 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 5:18 PM, <arun.sasi1(a)wipro.com> wrote:
Hello Stefan,
Thank you very much for considering my issue...
Here is My problem...
1) I have 4 VM`s Running on Base server.
2) Base server is having 15GB RAM.
3) I can start all VM`s apart from my file server.
4) File server is having OS image and 1.2TB QCOW2 Image.
5) When I remove 1.2TB from xml file (vdb.img) I can start my server
but
Data partition is null becase I have not added 1.2TB in XML.
6) Command I am using virsh start <Domain>
7) Even through virt-manager also I am not able to start the VM.
Attached is
the error message
Unfortunately the message gives no details:
"libvirtError: internal error unable to start guest:"
8) Keep on trying adding and removing and defining the XML after 2
Hrs
I am
able to start.
What did you change that made it work?
9) Operating system Ubuntu 9.04
10) I have 3 location file server having the same issue... even all
file
servers are same configuration...
Libvirt keeps log files for each VM under
/var/log/libvirt/qemu/<domain>.log. You might find more detailed
error information in that file and it will at least contain the
qemu-kvm command-line used to launch the domain. Please take a look
at that file and post the lines surrounding the error, especially the
"starting up" log line.
Have you verified that the .qcow2 image file is accessible, ownership
and permissions should be the same as the image files of your other
domains.
Stefan
-----Original Message-----
From: Stefan Hajnoczi [mailto:stefanha@linux.vnet.ibm.com]
Sent: Wednesday, May 18, 2011 9:28 PM
To: Arun Sasi V (WI01 - Manage IT)
Subject: Re: Qcow2
On Wed, May 18, 2011 at 07:30:05PM +0530, arun.sasi1(a)wipro.com wrote:
> The Guest VM which is larger example 1.2TB is not starting after
the
> base server reboot... Pleae help what needs to be do in this
situation.
You have not provided information on what is happening. Are you
getting
an error message during boot from the 1.2TB guest? Is the 1.2TB
guest
even being autostarted (use "virsh autostart
<domain>" to enable
autostart on a domain)?
Please send support questions like this to qemu-devel(a)nongnu.org in
the
future. That way other people in the QEMU community can help too.
Stefan
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any
attachments to
this message are intended for the exclusive use of the addressee(s)
and may
contain proprietary, confidential or privileged information. If you
are not
the intended recipient, you should not disseminate, distribute or
copy
this
e-mail. Please notify the sender immediately and destroy all copies
of
this
message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient
should
check this email and any attachments for the presence of viruses. The
company accepts no liability for any damage caused by any virus
transmitted
by this email.