[Libvir] Error when paravirtualization domain starts with virsh.
With the RHEL5 RC distribution on our IA64 platform (4 CPUs), when we use virsh to start a paravirtuailzation domain, we've got the following: virsh # list Id Name State ---------------------------------- 0 Domain-0 running virsh # create hndom2 Failed to get devices for domain hndom2 error: Failed to create domain from hndom2 virsh # list Id Name State ---------------------------------- 0 Domain-0 running 24 Domain-24 paused In spite of an error message, a domain named Domain-Id is created instead of the hndom2 domain. The corresponding XML configuration file is the following: <domain type="xen"> <name>hndom2</name> <os> <type>linux</type> <kernel>/boot/efi/efi/redhat/vmlinuz-2.6.18-8.el5xen</kernel> <root>/dev/hda1</root> <initrd>/boot/efi/efi/redhat/initrd-2.6.18-8.el5xenU.img</initrd> <cmdline>console=tty0 nomca 3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe selinux=0</cmdline> </os> <memory>527360</memory> <currentMemory>393216</currentMemory> <vcpu>3</vcpu> <on_poweroff>restart</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <disk type="block"> <driver name="phy"/> <source dev="/dev/sda5"/> <target dev="/dev/hda1"/> </disk> <interface type="bridge"> <source bridge=""/> </interface> </devices> </domain> If the <currentMemory> tag is suppressed from the XML configuration file, all is OK. This behaviour appears with the libvirt version 0.1.8 released with the RHEL5 RC, and also with the libvirt version 0.1.10. Are you aware of this problem? If you want some complementary infos (xend log), we can send it to you. Regards, Michel Gauthier.
On Mon, Mar 05, 2007 at 11:19:03AM +0100, Michel Gauthier wrote:
With the RHEL5 RC distribution on our IA64 platform (4 CPUs), when we use virsh to start a paravirtuailzation domain, we've got the following:
virsh # list Id Name State ---------------------------------- 0 Domain-0 running
virsh # create hndom2 Failed to get devices for domain hndom2 error: Failed to create domain from hndom2
virsh # list Id Name State ---------------------------------- 0 Domain-0 running 24 Domain-24 paused
In spite of an error message, a domain named Domain-Id is created instead of the hndom2 domain.
Yeah, that's a bug in libvirt - we failed to tear down the 'still born' domain when something goes wrong during creation.
If the <currentMemory> tag is suppressed from the XML configuration file, all is OK.
Sounds like a bug in Xen ia64 to me - the <currentMemory> is used to set the initial boot RAM, while the <memory> tag is used to set the maximum reservation. If you omit <currentMemory> then both will be set to the same value. It sounds like Xen ia64 is not able to cope with the memory < maxmem situation. memory=200 maxmem=500
This behaviour appears with the libvirt version 0.1.8 released with the RHEL5 RC, and also with the libvirt version 0.1.10. Are you aware of this problem?
No - we don't do much (any) testing on ia64 due to lack of any suitable hardware for testing, so we pretty much rely on community/vendors to identify ia64 problems.
If you want some complementary infos (xend log), we can send it to you.
See if you can reproduce it with a regular Xen config file using config options like memory=200 maxmem=500 Which should simlute presece of '<currentMemory>' element. If you can reproduce it there, its a Xen bug. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
Hi, Michel From Dan's suggestion, This issue seems related to DomU memory=256M case. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207241 To avoid this problem, you should set memory=512MB at first. Anyway, we are not checking virsh command on PV-domain/IA64 for RHEL5. I guess you are the first person to check virsh on PV-domain/IA64! Thanks Atsushi SAKAI "Daniel P. Berrange" <berrange@redhat.com> wrote:
On Mon, Mar 05, 2007 at 11:19:03AM +0100, Michel Gauthier wrote:
With the RHEL5 RC distribution on our IA64 platform (4 CPUs), when we use virsh to start a paravirtuailzation domain, we've got the following:
virsh # list Id Name State ---------------------------------- 0 Domain-0 running
virsh # create hndom2 Failed to get devices for domain hndom2 error: Failed to create domain from hndom2
virsh # list Id Name State ---------------------------------- 0 Domain-0 running 24 Domain-24 paused
In spite of an error message, a domain named Domain-Id is created instead of the hndom2 domain.
Yeah, that's a bug in libvirt - we failed to tear down the 'still born' domain when something goes wrong during creation.
If the <currentMemory> tag is suppressed from the XML configuration file, all is OK.
Sounds like a bug in Xen ia64 to me - the <currentMemory> is used to set the initial boot RAM, while the <memory> tag is used to set the maximum reservation. If you omit <currentMemory> then both will be set to the same value. It sounds like Xen ia64 is not able to cope with the memory < maxmem situation.
memory=200 maxmem=500
This behaviour appears with the libvirt version 0.1.8 released with the RHEL5 RC, and also with the libvirt version 0.1.10. Are you aware of this problem?
No - we don't do much (any) testing on ia64 due to lack of any suitable hardware for testing, so we pretty much rely on community/vendors to identify ia64 problems.
If you want some complementary infos (xend log), we can send it to you.
See if you can reproduce it with a regular Xen config file using config options like
memory=200 maxmem=500
Which should simlute presece of '<currentMemory>' element. If you can reproduce it there, its a Xen bug.
Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Hi, I confirm it's a Xen bug. I can reproduce the problem with a regular Xen config file. The file is as follow: [root@diane-int6 xen]# cat xen1 kernel = "/boot/efi/efi/redhat/vmlinuz-2.6.18-8.el5xen" ramdisk = "/boot/efi/efi/redhat/initrd-2.6.18-8.el5xenU.img" maxmem = 512 memory = 431 name = "xen1" cpus = "0-2,4,^1" vcpus = 2 vif = [ '' ] disk = [ 'phy:/dev/sda4,hda1,w' ] root = "/dev/hda1 ro" extra = "console=tty0 nomca 3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" [root@diane-int6 xen]# xm create xen1 Using config file "./xen1". Xend has probably crashed! Invalid or missing HTTP status code. [root@diane-int6 xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1008 1 r----- 123.5 Domain-2 2 431 1 --p--- 0.0 [root@diane-int6 xen]# A domain named Domain-2 is created instead of xen1. The Xend log shows that Xend died due to signal 11 and then is restarted. Regards. ----- Original Message ----- From: "Daniel P. Berrange" <berrange@redhat.com> To: "Michel Gauthier" <Michel.Gauthier@bull.net> Cc: <libvir-list@redhat.com> Sent: Monday, March 05, 2007 5:56 PM Subject: Re: [Libvir] Error when paravirtualization domain starts with virsh.
On Mon, Mar 05, 2007 at 11:19:03AM +0100, Michel Gauthier wrote:
With the RHEL5 RC distribution on our IA64 platform (4 CPUs), when we use virsh to start a paravirtuailzation domain, we've got the following:
virsh # list Id Name State ---------------------------------- 0 Domain-0 running
virsh # create hndom2 Failed to get devices for domain hndom2 error: Failed to create domain from hndom2
virsh # list Id Name State ---------------------------------- 0 Domain-0 running 24 Domain-24 paused
In spite of an error message, a domain named Domain-Id is created instead of the hndom2 domain.
Yeah, that's a bug in libvirt - we failed to tear down the 'still born' domain when something goes wrong during creation.
If the <currentMemory> tag is suppressed from the XML configuration file, all is OK.
Sounds like a bug in Xen ia64 to me - the <currentMemory> is used to set the initial boot RAM, while the <memory> tag is used to set the maximum reservation. If you omit <currentMemory> then both will be set to the same value. It sounds like Xen ia64 is not able to cope with the memory < maxmem situation.
memory=200 maxmem=500
This behaviour appears with the libvirt version 0.1.8 released with the RHEL5 RC, and also with the libvirt version 0.1.10. Are you aware of this problem?
No - we don't do much (any) testing on ia64 due to lack of any suitable hardware for testing, so we pretty much rely on community/vendors to identify ia64 problems.
If you want some complementary infos (xend log), we can send it to you.
See if you can reproduce it with a regular Xen config file using config options like
memory=200 maxmem=500
Which should simlute presece of '<currentMemory>' element. If you can reproduce it there, its a Xen bug.
Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: .cpan.org/~danberr/ -=| |=- Projects: at.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 505 -=|
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
participants (3)
-
Atsushi SAKAI -
Daniel P. Berrange -
Michel Gauthier