Hello Stephen,

Any update on this... what could be the reason... If I am not able to
start VM and if I add two virtual hard disk and one virtual hard disk is
more than 500GB.

Virtual harddisk type is virtio. Created by using qcow2

Thanks,
-Arun

-----Original Message-----
From: Arun Sasi V (WI01 - Manage IT)
Sent: Monday, May 30, 2011 3:02 PM
To: 'Stefan Hajnoczi'
Cc: 'stefa...@linux.vnet.ibm.com'; 'qemu-devel@nongnu.org';
'libvirt-us...@redhat.com'
Subject: RE: [Qemu-devel] Qcow2

Hello Team,

Please help me to solve this...

Find the below error

May 30 12:21:29 sd0005srv01 kernel: [19836592.317217] device vnet0
entered promiscuous mode
May 30 12:21:29 sd0005srv01 kernel: [19836592.319449] br0: port 2(vnet0)
entering learning state
May 30 12:21:29 sd0005srv01 nm-system-settings:    SCPlugin-Ifupdown:
device added (udi: /org/freedesktop/Hal/devices/net_ce_1b_36_05_70_14,
iface: vnet0): not well known
May 30 12:21:30 sd0005srv01 avahi-daemon[3449]: Registering new address
record for fe80::cc1b:36ff:fe05:7014 on vnet0.*.
May 30 12:21:33 sd0005srv01 nm-system-settings: Added default wired
connection 'Auto vnet0' for
/org/freedesktop/Hal/devices/net_ce_1b_36_05_70_14
May 30 12:21:38 sd0005srv01 kernel: [19836601.316008] br0: topology
change detected, propagating
May 30 12:21:38 sd0005srv01 kernel: [19836601.316014] br0: port 2(vnet0)
entering forwarding state
May 30 12:21:39 sd0005srv01 kernel: [19836602.949751] vnet0: no IPv6
routers present
May 30 12:21:59 sd0005srv01 libvirtd: 12:21:59.278: error : internal
error Timed out while reading console log output
May 30 12:21:59 sd0005srv01 libvirtd: 12:21:59.278: error : internal
error unable to start guest:
May 30 12:21:59 sd0005srv01 avahi-daemon[3449]: Withdrawing address
record for fe80::cc1b:36ff:fe05:7014 on vnet0.
May 30 12:21:59 sd0005srv01 kernel: [19836622.479659] br0: port 2(vnet0)
entering disabled state
May 30 12:21:59 sd0005srv01 kernel: [19836622.493771] device vnet0 left
promiscuous mode
May 30 12:21:59 sd0005srv01 kernel: [19836622.493773] br0: port 2(vnet0)
entering disabled state
May 30 12:21:59 sd0005srv01 nm-system-settings:    SCPlugin-Ifupdown:
devices removed (udi: /org/freedesktop/Hal/



Thanks,
-Arun


-----Original Message-----
From: Arun Sasi V (WI01 - Manage IT)
Sent: Monday, May 30, 2011 2:24 PM
To: 'Stefan Hajnoczi'
Cc: 'stefa...@linux.vnet.ibm.com'; 'qemu-devel@nongnu.org';
'libvirt-us...@redhat.com'
Subject: RE: [Qemu-devel] Qcow2

Hello Stefan,

I can see some error messages

May 30 11:36:49 sd0005srv01 libvirtd: 11:36:49.044: error : internal
error Timed out while reading console log output
May 30 11:36:49 sd0005srv01 libvirtd: 11:36:49.044: error : internal
error unable to start guest:

I am using ubuntu 9.04

Thanks,
-Arun

-----Original Message-----
From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
Sent: Friday, May 20, 2011 12:35 AM
To: Arun Sasi V (WI01 - Manage IT)
Cc: stefa...@linux.vnet.ibm.com; qemu-devel@nongnu.org;
libvirt-us...@redhat.com
Subject: Re: [Qemu-devel] Qcow2

On Thu, May 19, 2011 at 3:24 PM,  <arun.sa...@wipro.com> wrote:
> I couldn't find any error when I do consistency check on the image
file...

Good, so there are no problems with your data.

> What can be the reason for not starting the VM.

Did you find any more error messages besides the sound related errors
in /var/log/libvirt/qemu/<domain>.log?

> 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...

No, there is no "cache creation".  There is no startup delay for qcow2
image files.

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. 

www.wipro.com

Reply via email to