Hi all
This is the first time I try and get Xen working, and want to install a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server.
Trying to get the first one to install is rather trivial, and I keep on running into errors. At fist I wanted to install it fro the cdrom, so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could choose my language, but then got an error saying I don't have the right driver for the cdrom install. Odd.
So, I copied the whole CD to my intranet server, to try a HTTP installation, which got much further, but fails as soon as it starts copying the files to the xvda partition.
Here's what I've done: virt-install -p --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 --file=/vm/vm03.img --name=vm03
Probing for video card: Unable to probe No video hardware found, assuming headless Graphical installation not available... Starting text mode. Welcome to CentOS
+------------------+ Package Installation +------------------+ | | | Name : libXt-1.0.2-3.1.fc6-i386 | | Size : 359k | | Summary: X.Org X11 libXt runtime library | | | | | | Status: | | | | 53% | | | | Packages Bytes Time | | Total : 349 564M 0:02:30 | | Completed: 123 200M 0:00:53 | | Remaining: 226 364M 0:01:37 | | | | 35% Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm03'; otherwise, pleasels | <F12> next screen restart your installation. [root@gimbli ~]# virsh start vm03 libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") error: Failed to start domain vm03
/var/log/messages got filled with the following messages:
stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability
What am I doing wrong?
Rudi Ahlers wrote:
Hi all
This is the first time I try and get Xen working, and want to install a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server.
Trying to get the first one to install is rather trivial, and I keep on running into errors. At fist I wanted to install it fro the cdrom, so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could choose my language, but then got an error saying I don't have the right driver for the cdrom install. Odd.
So, I copied the whole CD to my intranet server, to try a HTTP installation, which got much further, but fails as soon as it starts copying the files to the xvda partition.
Here's what I've done: virt-install -p --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 --file=/vm/vm03.img --name=vm03
Probing for video card: Unable to probe No video hardware found, assuming headless Graphical installation not available... Starting text mode. Welcome to CentOS
+------------------+ Package Installation +------------------+ | | | Name : libXt-1.0.2-3.1.fc6-i386 | | Size : 359k | | Summary: X.Org X11 libXt runtime library | | | | | | Status: | | | | 53% | | | | Packages Bytes Time | | Total : 349 564M 0:02:30 | | Completed: 123 200M 0:00:53 | | Remaining: 226 364M 0:01:37 | | | | 35%Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm03'; otherwise, pleasels | <F12> next screen restart your installation. [root@gimbli ~]# virsh start vm03 libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") error: Failed to start domain vm03
/var/log/messages got filled with the following messages:
stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability
What am I doing wrong?
as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU on a 64bit dom0 is not supported and known to crash
Tom Brown wrote:
Rudi Ahlers wrote:
Hi all
This is the first time I try and get Xen working, and want to install a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server.
Trying to get the first one to install is rather trivial, and I keep on running into errors. At fist I wanted to install it fro the cdrom, so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could choose my language, but then got an error saying I don't have the right driver for the cdrom install. Odd.
So, I copied the whole CD to my intranet server, to try a HTTP installation, which got much further, but fails as soon as it starts copying the files to the xvda partition.
Here's what I've done: virt-install -p --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 --file=/vm/vm03.img --name=vm03
Probing for video card: Unable to probe No video hardware found, assuming headless Graphical installation not available... Starting text mode. Welcome to CentOS
+------------------+ Package Installation +------------------+ | | | Name : libXt-1.0.2-3.1.fc6-i386 | | Size : 359k | | Summary: X.Org X11 libXt runtime library | | | | | | Status: | | | | 53% | | | | Packages Bytes Time | | Total : 349 564M 0:02:30 | | Completed: 123 200M 0:00:53 | | Remaining: 226 364M 0:01:37 | | | | 35%Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm03'; otherwise, pleasels | <F12> next screen restart your installation. [root@gimbli ~]# virsh start vm03 libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") error: Failed to start domain vm03
/var/log/messages got filled with the following messages:
stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability
What am I doing wrong?
as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU on a 64bit dom0 is not supported and known to crash
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Are you sure? I've read on a few different sites / emails that people do this, mainly because the 64bit version can handle the large amounts of memory typically found in dedicated servers.
Are you sure? I've read on a few different sites / emails that people do this, mainly because the 64bit version can handle the large amounts of memory typically found in dedicated servers.
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Virtualization-e...
"With Red Hat Virtualization, 32-bit hosts runs only 32-bit paravirtual guests. 64-bit hosts runs only 64-bit paravirtual guests. And a 64-bit full virtualization host runs 32-bit, 32-bit PAE, or 64-bit guests. A 32-bit full virtualization host runs both PAE and non-PAE full virtualization guests."
Tom Brown wrote:
Are you sure? I've read on a few different sites / emails that people do this, mainly because the 64bit version can handle the large amounts of memory typically found in dedicated servers.
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Virtualization-e...
"With Red Hat Virtualization, 32-bit hosts runs only 32-bit paravirtual guests. 64-bit hosts runs only 64-bit paravirtual guests. And a 64-bit full virtualization host runs 32-bit, 32-bit PAE, or 64-bit guests. A 32-bit full virtualization host runs both PAE and non-PAE full virtualization guests."
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yes, so I can run 32bit guests on 64bit host,but with full virtualization. How do I know if a) my system supports it, and b) my kernel / OS has full virtualization enabled?
I have an intel Core 2 Duo 6750 CPU, which has Intel VT, and it's enabled in the BIOS, as can be seen here:
[root@gimbli ~]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping : 11 cpu MHz : 2666.742 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 cx16 xtpr lahf_lm bogomips : 6669.70 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping : 11 cpu MHz : 2666.742 cache size : 4096 KB physical id : 1 siblings : 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 cx16 xtpr lahf_lm bogomips : 6669.70 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
What else do I need todo?
uname -a Linux gimbli 2.6.18-53.1.13.el5xen #1 SMP Tue Feb 12 13:33:07 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
Tom Brown wrote:
Rudi Ahlers wrote:
Hi all
This is the first time I try and get Xen working, and want to install a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server.
Trying to get the first one to install is rather trivial, and I keep on running into errors. At fist I wanted to install it fro the cdrom, so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could choose my language, but then got an error saying I don't have the right driver for the cdrom install. Odd.
So, I copied the whole CD to my intranet server, to try a HTTP installation, which got much further, but fails as soon as it starts copying the files to the xvda partition.
Here's what I've done: virt-install -p --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 --file=/vm/vm03.img --name=vm03
Probing for video card: Unable to probe No video hardware found, assuming headless Graphical installation not available... Starting text mode. Welcome to CentOS
+------------------+ Package Installation +------------------+ | | | Name : libXt-1.0.2-3.1.fc6-i386 | | Size : 359k | | Summary: X.Org X11 libXt runtime library | | | | | | Status: | | | | 53% | | | | Packages Bytes Time | | Total : 349 564M 0:02:30 | | Completed: 123 200M 0:00:53 | | Remaining: 226 364M 0:01:37 | | | | 35%Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm03'; otherwise, pleasels | <F12> next screen restart your installation. [root@gimbli ~]# virsh start vm03 libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") error: Failed to start domain vm03
/var/log/messages got filled with the following messages:
stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability
What am I doing wrong?
as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU on a 64bit dom0 is not supported and known to crash
That's incorrent. I have three Rhel5.1 x86_64 xenhosts with different 32 bits domU, centos 5.1, centos 5.0 and rhel5.1 included ...
I think that problem is selinux. In redhat docs explains that domU needs to reside on /var/lib/xen if you use selinux. You can try to disable selinux (/etc/sysconfig/selinux) and all works ok.
carlopmart wrote:
Tom Brown wrote:
Rudi Ahlers wrote:
Hi all
This is the first time I try and get Xen working, and want to install a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server.
Trying to get the first one to install is rather trivial, and I keep on running into errors. At fist I wanted to install it fro the cdrom, so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could choose my language, but then got an error saying I don't have the right driver for the cdrom install. Odd.
So, I copied the whole CD to my intranet server, to try a HTTP installation, which got much further, but fails as soon as it starts copying the files to the xvda partition.
Here's what I've done: virt-install -p --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 --file=/vm/vm03.img --name=vm03
Probing for video card: Unable to probe No video hardware found, assuming headless Graphical installation not available... Starting text mode. Welcome to CentOS
+------------------+ Package Installation +------------------+ | | | Name : libXt-1.0.2-3.1.fc6-i386 | | Size : 359k | | Summary: X.Org X11 libXt runtime library | | | | | | Status: | | | | 53% | | | | Packages Bytes Time | | Total : 349 564M 0:02:30 | | Completed: 123 200M 0:00:53 | | Remaining: 226 364M 0:01:37 | | | | 35%Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm03'; otherwise, pleasels | <F12> next screen restart your installation. [root@gimbli ~]# virsh start vm03 libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") error: Failed to start domain vm03
/var/log/messages got filled with the following messages:
stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability
What am I doing wrong?
as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU on a 64bit dom0 is not supported and known to crash
That's incorrent. I have three Rhel5.1 x86_64 xenhosts with different 32 bits domU, centos 5.1, centos 5.0 and rhel5.1 included ...
I think that problem is selinux. In redhat docs explains that domU needs to reside on /var/lib/xen if you use selinux. You can try to disable selinux (/etc/sysconfig/selinux) and all works ok.
I have got selinux disabled.
Rudi Ahlers wrote:
carlopmart wrote:
Tom Brown wrote:
Rudi Ahlers wrote:
Hi all
This is the first time I try and get Xen working, and want to install a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server.
Trying to get the first one to install is rather trivial, and I keep on running into errors. At fist I wanted to install it fro the cdrom, so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could choose my language, but then got an error saying I don't have the right driver for the cdrom install. Odd.
So, I copied the whole CD to my intranet server, to try a HTTP installation, which got much further, but fails as soon as it starts copying the files to the xvda partition.
Here's what I've done: virt-install -p --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 --file=/vm/vm03.img --name=vm03
Probing for video card: Unable to probe No video hardware found, assuming headless Graphical installation not available... Starting text mode. Welcome to CentOS
+------------------+ Package Installation +------------------+ | | | Name : libXt-1.0.2-3.1.fc6-i386 | | Size : 359k | | Summary: X.Org X11 libXt runtime library | | | | | | Status: | | | | 53% | | | | Packages Bytes Time | | Total : 349 564M 0:02:30 | | Completed: 123 200M 0:00:53 | | Remaining: 226 364M 0:01:37 | | | | 35%Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm03'; otherwise, pleasels | <F12> next screen restart your installation. [root@gimbli ~]# virsh start vm03 libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") error: Failed to start domain vm03
/var/log/messages got filled with the following messages:
stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability
What am I doing wrong?
as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU on a 64bit dom0 is not supported and known to crash
That's incorrent. I have three Rhel5.1 x86_64 xenhosts with different 32 bits domU, centos 5.1, centos 5.0 and rhel5.1 included ...
I think that problem is selinux. In redhat docs explains that domU needs to reside on /var/lib/xen if you use selinux. You can try to disable selinux (/etc/sysconfig/selinux) and all works ok.
I have got selinux disabled.
Are you sure?? Then, why on your /var/log/messages selinux errors appears??
That's incorrent. I have three Rhel5.1 x86_64 xenhosts with different 32 bits domU, centos 5.1, centos 5.0 and rhel5.1 included ...
I think that problem is selinux. In redhat docs explains that domU needs to reside on /var/lib/xen if you use selinux. You can try to disable selinux (/etc/sysconfig/selinux) and all works ok.
I have got selinux disabled.
Are you sure?? Then, why on your /var/log/messages selinux errors appears??
Ok, I've disabled selinux (again) and rebooted, but still get the same error:
Welcome to CentOS
+------------------+ Package Installation +------------------+ | | | Name : | | Size : | | Summary: | | | | | | Status:+---------+ Install Starting +----------+ | | | | | | | Starting install process. This may | | | | take several minutes... | | | | | Time | | Total +---------------------------------------+ | | Complet | | Remaining: 355 575M | | | | 0% | | | +------------------------------------------------------------+
sending termination signals...done sending kill signals...done disabling swap... /dev/mapper/VolGroup00-LogVol01 unmounting filesystems... /mnt/runtime done disabling /dev/loop0 /proc done /dev/pts done /sys done /tmp/ramfs done /selinux done /mnt/sysimage/boot done /mnt/sysimage/sys done /mnt/sysimage/proc done /mnt/sysimage/selinux done /mnt/sysimage/dev done /mnt/sysimage done rebooting system Restarting system. Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm02'; otherwise, please restart your installation.
This time it didn't see a package from the network server, and I told it to reboot, just to see what happens....
What controls the boot loader that it's complaining about?
-
carlopmart -
Rudi Ahlers -
Tom Brown