Re: [libvirt-users] [Qemu-devel] Qcow2
On Wed, May 18, 2011 at 5:18 PM, <arun.sasi1@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@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@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.
www.wipro.com
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@linux.vnet.ibm.com; qemu-devel@nongnu.org; libvirt-users@redhat.com Subject: Re: [Qemu-devel] Qcow2 On Wed, May 18, 2011 at 5:18 PM, <arun.sasi1@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@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@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.
www.wipro.com
On Wed, May 18, 2011 at 7:03 PM, <arun.sasi1@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
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@linux.vnet.ibm.com; qemu-devel@nongnu.org; libvirt-users@redhat.com Subject: Re: [Qemu-devel] Qcow2 On Wed, May 18, 2011 at 7:03 PM, <arun.sasi1@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
On Thu, May 19, 2011 at 3:24 PM, <arun.sasi1@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
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:stefanha@gmail.com] Sent: Friday, May 20, 2011 12:35 AM To: Arun Sasi V (WI01 - Manage IT) Cc: stefanha@linux.vnet.ibm.com; qemu-devel@nongnu.org; libvirt-users@redhat.com Subject: Re: [Qemu-devel] Qcow2 On Thu, May 19, 2011 at 3:24 PM, <arun.sasi1@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.
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
Did you find any more error messages besides the sound related errors in /var/log/libvirt/qemu/<domain>.log? 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
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: 'stefanha@linux.vnet.ibm.com'; 'qemu-devel@nongnu.org'; 'libvirt-users@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:stefanha@gmail.com] Sent: Friday, May 20, 2011 12:35 AM To: Arun Sasi V (WI01 - Manage IT) Cc: stefanha@linux.vnet.ibm.com; qemu-devel@nongnu.org; libvirt-users@redhat.com Subject: Re: [Qemu-devel] Qcow2 On Thu, May 19, 2011 at 3:24 PM, <arun.sasi1@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.
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
Did you find any more error messages besides the sound related errors in /var/log/libvirt/qemu/<domain>.log? 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
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: 'stefanha@linux.vnet.ibm.com'; 'qemu-devel@nongnu.org'; 'libvirt-users@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: 'stefanha@linux.vnet.ibm.com'; 'qemu-devel@nongnu.org'; 'libvirt-users@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:stefanha@gmail.com] Sent: Friday, May 20, 2011 12:35 AM To: Arun Sasi V (WI01 - Manage IT) Cc: stefanha@linux.vnet.ibm.com; qemu-devel@nongnu.org; libvirt-users@redhat.com Subject: Re: [Qemu-devel] Qcow2 On Thu, May 19, 2011 at 3:24 PM, <arun.sasi1@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.
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
Did you find any more error messages besides the sound related errors in /var/log/libvirt/qemu/<domain>.log? 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
On Tue, Jun 7, 2011 at 6:10 PM, <arun.sasi1@wipro.com> wrote:
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
Sorry, nothing obvious from your error output. I recommend running a recent distro. Stefan
Hello Stephen. Error from Syslog 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: ------------------------- ---------------------------- 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/ ------------------------------------------------------ XML File ------------- <domain type='kvm'> <name>sy0005embinf02</name> <uuid>9ddfc4b5-51bc-c3e9-3aea-59101bc15174</uuid> <memory>4096000</memory> <currentMemory>524288</currentMemory> <vcpu>4</vcpu> <os> <type arch='x86_64' machine='pc'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file' device='cdrom'> <target dev='hdc' bus='ide'/> <readonly/> </disk> <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/sy0005embinf02.img'/> <target dev='vda' bus='virtio'/> </disk> <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/sy0005embinf02_vdb.img'/> <target dev='vdb' bus='virtio'/> </disk> <interface type='bridge'> <mac address='00:16:36:1d:67:9e'/> <source bridge='br0'/> <model type='virtio'/> </interface> <serial type='pty'> <source path='/dev/pts/11'/> <target port='0'/> </serial> <console type='pty' tty='/dev/pts/11'> <source path='/dev/pts/11'/> <target port='0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/> <sound model='es1370'/> </devices> </domain> Thanks, -Arun -----Original Message----- From: Stefan Hajnoczi [mailto:stefanha@gmail.com] Sent: Wednesday, June 08, 2011 1:49 PM To: Arun Sasi V (WI01 - Manage IT) Cc: stefanha@linux.vnet.ibm.com; qemu-devel@nongnu.org; libvirt-users@redhat.com Subject: Re: [Qemu-devel] Qcow2 On Tue, Jun 7, 2011 at 6:10 PM, <arun.sasi1@wipro.com> wrote:
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
Sorry, nothing obvious from your error output. I recommend running a recent distro. Stefan
Hello Stefan, I have a small query about virtualization. Need to install file server on Base server and include some virtual machines on that i.e. DNS/DHCP/LDAP etc. Will I get complete performance on file server since it is in Base server where KVM kernel installed... Thanks, -Arun
On Thu, Jun 16, 2011 at 03:26:25PM +0530, arun.sasi1@wipro.com wrote:
Will I get complete performance on file server since it is in Base server where KVM kernel installed...
Yes, applications running on the host will performance as normal. Remember that virtual machines consume CPU, memory, and other resources too though. That means busy VMs can affect application performance on the host. Stefan
No here my scenario is File server is in Base server. Ldap,DNS,DHCP is in KVM-VM So I want to know what will be the my file server performance. My confusion. Installed KVM on file server. So all paging and memory will allocate to Vm`s... Thanks, -Arun -----Original Message----- From: Stefan Hajnoczi [mailto:stefanha@linux.vnet.ibm.com] Sent: Thursday, June 16, 2011 4:07 PM To: Arun Sasi V (WI01 - Manage IT) Cc: stefanha@gmail.com; qemu-devel@nongnu.org; libvirt-users@redhat.com Subject: Re: Base server as file server. On Thu, Jun 16, 2011 at 03:26:25PM +0530, arun.sasi1@wipro.com wrote:
Will I get complete performance on file server since it is in Base server where KVM kernel installed...
Yes, applications running on the host will performance as normal. Remember that virtual machines consume CPU, memory, and other resources too though. That means busy VMs can affect application performance on the host. Stefan
participants (3)
-
arun.sasi1＠wipro.com -
Stefan Hajnoczi -
Stefan Hajnoczi