Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0.
Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities.
-Ross
----- Original Message ----- From: centos-bounces@centos.org centos-bounces@centos.org To: CentOS mailing list centos@centos.org Sent: Fri Feb 29 04:46:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1 x64
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
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
Ross S. W. Walker wrote:
Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0.
Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities.
-Ross
----- Original Message ----- From: centos-bounces@centos.org centos-bounces@centos.org To: CentOS mailing list centos@centos.org Sent: Fri Feb 29 04:46:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1 x64
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
Ok, so what do I do if I want to have a 64bit Host XEN & 32guest's? I'd prefer to use CentOS for this purpose, if possible
Ross S. W. Walker wrote:
Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0.
Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities.
-Ross
----- Original Message -----
I've run into an interesting problem, which trying to install a 64bit guest:
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.') Traceback (most recent call last): File "/usr/sbin/virt-install", line 633, in ? main() File "/usr/sbin/virt-install", line 578, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 649, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 666, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 503, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.')
[root@gimbli ~]# 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 [root@gimbli ~]# cat /proc/meminfo MemTotal: 713728 kB MemFree: 503028 kB Buffers: 25284 kB Cached: 69356 kB SwapCached: 0 kB Active: 67144 kB Inactive: 55820 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 713728 kB LowFree: 503028 kB SwapTotal: 2096472 kB SwapFree: 2096472 kB Dirty: 40 kB Writeback: 0 kB AnonPages: 28280 kB Mapped: 7584 kB Slab: 17004 kB PageTables: 2316 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 2453336 kB Committed_AS: 145988 kB VmallocTotal: 34359738367 kB VmallocUsed: 2204 kB VmallocChunk: 34359735799 kB
Even though Linux reports only 713MB RAM, the machine has 2GB RAM. How / where do I fix this?
Rudi Ahlers wrote:
Ross S. W. Walker wrote:
Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0.
Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities.
-Ross
----- Original Message -----
I've run into an interesting problem, which trying to install a 64bit guest:
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.') Traceback (most recent call last): File "/usr/sbin/virt-install", line 633, in ? main() File "/usr/sbin/virt-install", line 578, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 649, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 666, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 503, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.')
[root@gimbli ~]# 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 [root@gimbli ~]# cat /proc/meminfo MemTotal: 713728 kB MemFree: 503028 kB Buffers: 25284 kB Cached: 69356 kB SwapCached: 0 kB Active: 67144 kB Inactive: 55820 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 713728 kB LowFree: 503028 kB SwapTotal: 2096472 kB SwapFree: 2096472 kB Dirty: 40 kB Writeback: 0 kB AnonPages: 28280 kB Mapped: 7584 kB Slab: 17004 kB PageTables: 2316 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 2453336 kB Committed_AS: 145988 kB VmallocTotal: 34359738367 kB VmallocUsed: 2204 kB VmallocChunk: 34359735799 kB
Even though Linux reports only 713MB RAM, the machine has 2GB RAM. How / where do I fix this?
I also saw this:
xentop - 18:04:44 Xen 3.1.0-53.1.13.el5 4 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 2086396k total, 2076932k used, 9464k free CPUs: 2 @ 2666MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID Domain-0 -----r 122 1.6 713728 34.2 no limit n/a 2 4 4091 121100 0 0 0 0 0 vm01 --b--- 42 0.2 262000 12.6 262144 12.6 1 1 1680 98659 0 0 0 0 0
xen top shows the full RAM, but the system itself doesn't?
Rudi Ahlers wrote:
Rudi Ahlers wrote:
Ross S. W. Walker wrote:
Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on
64-bit dom0.
Actually RHEL Xen is 3.1 with the brain damaged 3.0
userland utilities.
-Ross
----- Original Message -----
I've run into an interesting problem, which trying to
install a 64bit
guest:
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.') Traceback (most recent call last): File "/usr/sbin/virt-install", line 633, in ? main() File "/usr/sbin/virt-install", line 578, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 649,
in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 666,
in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 503, in createLinux if ret is None:raise
libvirtError('virDomainCreateLinux() failed',
conn=self) libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.')
[root@gimbli ~]# 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 [root@gimbli ~]# cat /proc/meminfo MemTotal: 713728 kB MemFree: 503028 kB Buffers: 25284 kB Cached: 69356 kB SwapCached: 0 kB Active: 67144 kB Inactive: 55820 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 713728 kB LowFree: 503028 kB SwapTotal: 2096472 kB SwapFree: 2096472 kB Dirty: 40 kB Writeback: 0 kB AnonPages: 28280 kB Mapped: 7584 kB Slab: 17004 kB PageTables: 2316 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 2453336 kB Committed_AS: 145988 kB VmallocTotal: 34359738367 kB VmallocUsed: 2204 kB VmallocChunk: 34359735799 kB
Even though Linux reports only 713MB RAM, the machine has
2GB RAM. How
/ where do I fix this?
I also saw this:
xentop - 18:04:44 Xen 3.1.0-53.1.13.el5 4 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 2086396k total, 2076932k used, 9464k free CPUs: 2 @ 2666MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID Domain-0 -----r 122 1.6 713728 34.2 no limit n/a 2 4 4091 121100 0 0 0 0 0 vm01 --b--- 42 0.2 262000 12.6 262144 12.6 1 1 1680 98659 0 0 0 0 0
xen top shows the full RAM, but the system itself doesn't?
That's because 'free' or 'top' in dom0 is only going to show the memory allocated to dom0.
Don't forget dom0 is a virtual machine too!
'xm' top will show the total memory for the system.
I suggest removing the dom0_mem restriction in /boot/grub/menu.lst if you have it, and making sure (dom0-min-mem 512) is set in /etc/xen/xend-config.sxp, especially if you are using X on the system. This will make sure that dom0 will always have at least 512MB of mem available to it and if necessary can balloon out and shrink back.
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
Ross S. W. Walker wrote:
Rudi Ahlers wrote:
Rudi Ahlers wrote:
Ross S. W. Walker wrote:
Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on
64-bit dom0.
Actually RHEL Xen is 3.1 with the brain damaged 3.0
userland utilities.
-Ross
----- Original Message -----
I've run into an interesting problem, which trying to
install a 64bit
guest:
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.') Traceback (most recent call last): File "/usr/sbin/virt-install", line 633, in ? main() File "/usr/sbin/virt-install", line 578, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 649,
in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 666,
in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 503, in createLinux if ret is None:raise
libvirtError('virDomainCreateLinux() failed',
conn=self) libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.')
[root@gimbli ~]# 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 [root@gimbli ~]# cat /proc/meminfo MemTotal: 713728 kB MemFree: 503028 kB Buffers: 25284 kB Cached: 69356 kB SwapCached: 0 kB Active: 67144 kB Inactive: 55820 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 713728 kB LowFree: 503028 kB SwapTotal: 2096472 kB SwapFree: 2096472 kB Dirty: 40 kB Writeback: 0 kB AnonPages: 28280 kB Mapped: 7584 kB Slab: 17004 kB PageTables: 2316 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 2453336 kB Committed_AS: 145988 kB VmallocTotal: 34359738367 kB VmallocUsed: 2204 kB VmallocChunk: 34359735799 kB
Even though Linux reports only 713MB RAM, the machine has
2GB RAM. How
/ where do I fix this?
I also saw this:
xentop - 18:04:44 Xen 3.1.0-53.1.13.el5 4 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 2086396k total, 2076932k used, 9464k free CPUs: 2 @ 2666MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID Domain-0 -----r 122 1.6 713728 34.2 no limit n/a 2 4 4091 121100 0 0 0 0 0 vm01 --b--- 42 0.2 262000 12.6 262144 12.6 1 1 1680 98659 0 0 0 0 0
xen top shows the full RAM, but the system itself doesn't?
That's because 'free' or 'top' in dom0 is only going to show the memory allocated to dom0.
Don't forget dom0 is a virtual machine too!
'xm' top will show the total memory for the system.
I suggest removing the dom0_mem restriction in /boot/grub/menu.lst if you have it, and making sure (dom0-min-mem 512) is set in /etc/xen/xend-config.sxp, especially if you are using X on the system. This will make sure that dom0 will always have at least 512MB of mem available to it and if necessary can balloon out and shrink back.
Thanx.
There was no dom0_mem restriction in /boot/grub/menu.list, but the
(dom0-min-mem 256) in /etc/xen/xend-config.sxp was a bit low, so I adjusted it to 512, so now free -m shows quite a bit more RAM on the system.
I have send in a request to join centos-virt@centos.org - but apparently someone needs to approve me as a list user.... I'd really like to get this think cracking :(
Rudi Ahlers wrote:
Ross S. W. Walker wrote:
Rudi Ahlers wrote:
Rudi Ahlers wrote:
Ross S. W. Walker wrote:
Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on
64-bit dom0.
Actually RHEL Xen is 3.1 with the brain damaged 3.0
userland utilities.
-Ross
----- Original Message -----
I've run into an interesting problem, which trying to
install a 64bit
guest:
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.') Traceback (most recent call last): File "/usr/sbin/virt-install", line 633, in ? main() File "/usr/sbin/virt-install", line 578, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 649,
in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 666,
in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 503, in createLinux if ret is None:raise
libvirtError('virDomainCreateLinux() failed',
conn=self) libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err 'Error creating domain: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 461040 KiB free.')
[root@gimbli ~]# 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 [root@gimbli ~]# cat /proc/meminfo MemTotal: 713728 kB MemFree: 503028 kB Buffers: 25284 kB Cached: 69356 kB SwapCached: 0 kB Active: 67144 kB Inactive: 55820 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 713728 kB LowFree: 503028 kB SwapTotal: 2096472 kB SwapFree: 2096472 kB Dirty: 40 kB Writeback: 0 kB AnonPages: 28280 kB Mapped: 7584 kB Slab: 17004 kB PageTables: 2316 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 2453336 kB Committed_AS: 145988 kB VmallocTotal: 34359738367 kB VmallocUsed: 2204 kB VmallocChunk: 34359735799 kB
Even though Linux reports only 713MB RAM, the machine has
2GB RAM. How
/ where do I fix this?
I also saw this:
xentop - 18:04:44 Xen 3.1.0-53.1.13.el5 4 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 2086396k total, 2076932k used, 9464k free CPUs: 2 @ 2666MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID Domain-0 -----r 122 1.6 713728 34.2 no limit n/a 2 4 4091 121100 0 0 0 0 0 vm01 --b--- 42 0.2 262000 12.6 262144 12.6 1 1 1680 98659 0 0 0 0 0
xen top shows the full RAM, but the system itself doesn't?
That's because 'free' or 'top' in dom0 is only going to show the memory allocated to dom0.
Don't forget dom0 is a virtual machine too!
'xm' top will show the total memory for the system.
I suggest removing the dom0_mem restriction in /boot/grub/menu.lst if you have it, and making sure (dom0-min-mem 512) is set in /etc/xen/xend-config.sxp, especially if you are using X on the system. This will make sure that dom0 will always have at least 512MB of mem available to it and if necessary can balloon out and shrink back.
<snip junk>
Thanx.
There was no dom0_mem restriction in /boot/grub/menu.list, but the
(dom0-min-mem 256) in /etc/xen/xend-config.sxp was a bit low, so I adjusted it to 512, so now free -m shows quite a bit more RAM on the system.
I have send in a request to join centos-virt@centos.org - but apparently someone needs to approve me as a list user.... I'd really like to get this think cracking :(
That shouldn't be, the list acts like any other CentOS list, maybe you entered your email address incorrectly, got spam filtered, or is just temporarily broken, but it should send you an email upon subscribing to confirm your subscription.
Did you verify that selinux is indeed disabled by looking in /etc/selinux/config that the line SELINUX=disabled is in there?
What was the actual contents of your domU's config file?
Also is this a workstation with Xen domU's for testing/development or a full blown Xen server for running production VMs?
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
That shouldn't be, the list acts like any other CentOS list, maybe you entered your email address incorrectly, got spam filtered, or is just temporarily broken, but it should send you an email upon subscribing to confirm your subscription.
Really? Maybe I subscribed to the wrong list then, but this is the reply I got:
Your mail to 'CentOS-virt' with the subject
subscribe centos-virt
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message may contain administrivia
Did you verify that selinux is indeed disabled by looking in /etc/selinux/config that the line SELINUX=disabled is in there?
Yep:
# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
What was the actual contents of your domU's config file?
This is what I changed:
# Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 512)
It was: (dom0-min-mem 256)
Also is this a workstation with Xen domU's for testing/development or a full blown Xen server for running production VMs?
-Ross
This will be a full blown Xen server for production purposes. It will run max 8 Xen guests with cPanel on each one.
Rudi Ahlers wrote:
Ross S. W. Walker wrote:
That shouldn't be, the list acts like any other CentOS list, maybe you entered your email address incorrectly, got spam filtered, or is just temporarily broken, but it should send you an email upon subscribing to confirm your subscription.
Really? Maybe I subscribed to the wrong list then, but this is the reply I got:
Your mail to 'CentOS-virt' with the subject
subscribe centos-virtIs being held until the list moderator can review it for approval.
The reason it is being held:
Message may contain administrivia
Try subscribing through the mailman web site:
http://lists.centos.org/mailman/listinfo
Did you verify that selinux is indeed disabled by looking in /etc/selinux/config that the line SELINUX=disabled is in there?
Yep:
# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
Good, just some users use setenforce 0 and think that's it done and then reboot and wonder why things are still not working properly.
What was the actual contents of your domU's config file?
This is what I changed:
# Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 512)
It was: (dom0-min-mem 256)
Misunderstanding, I was hoping to see the config file of the domU you were trying to create.
Also is this a workstation with Xen domU's for testing/development or a full blown Xen server for running production VMs?
-Ross
This will be a full blown Xen server for production purposes. It will run max 8 Xen guests with cPanel on each one.
In that case if you don't want to shell out the $ for Xen Enterprise I would do these steps for setting up a Xen server:
- for each server, minimal install, no X to reduce any possible dom0 issues, and to allow you to minimize dom0 memory usage, you can then run in 256MB with no X windows!
- use the Xen 3.2 packages off of xen.org, compiled 64-bit, compile on separate 64-bit platform as the compilation will pull in a lot of other development packages and X. These packages use the Xen kernel from CentOS for the kernel image, and that package comes with the 3.1 Xen image so you'll need to edit the grub.conf to make sure the Xen 3.2 image is used instead of the 3.1 image every time you upgrade the kernel. These packages provide the latest features and fixes as well as the more capable management tools and API which will become a necessity when you manage from the command line and/or have more then 1 server which eventually you will for scalability, redundancy, etc.
- Start seriously thinking about implementing an iSCSI SAN, your storage requirements will balloon crazy until your virtualization environment stabilizes, and SANs allows for better storage utilization, scalability and also allows for VM migration from one host to another and are a bitch to migrate to after the fact.
- Build your Xen config files by hand, it's the only way to assure they are setup properly and the way you want.
Since a Xen environment will be sensitive to change, maybe not as much as a LAMP environment, but still probably second to, you may want to manage your Xen build yourself, at least for the servers, as Redhat's Xen implementation is still evolving.
I would use Redhat's Xen environments once they have a pure Xen 3.2 build, as their current Frankenstein environment is really aimed at workstation deployments, especially their hoaky X tool.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
Ross S. W. Walker wrote:
Rudi Ahlers wrote:
Ross S. W. Walker wrote:
That shouldn't be, the list acts like any other CentOS list, maybe you entered your email address incorrectly, got spam filtered, or is just temporarily broken, but it should send you an email upon subscribing to confirm your subscription.
Really? Maybe I subscribed to the wrong list then, but this is the reply I got:
Your mail to 'CentOS-virt' with the subject
subscribe centos-virtIs being held until the list moderator can review it for approval.
The reason it is being held:
Message may contain administriviaTry subscribing through the mailman web site:
Odd, my subscription did go though on the first email, as I got a message saying I'm already subscribed. I'll post there as well, let's see what happens :)
Did you verify that selinux is indeed disabled by looking in /etc/selinux/config that the line SELINUX=disabled is in there?
Yep:
# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
Good, just some users use setenforce 0 and think that's it done and then reboot and wonder why things are still not working properly.
What was the actual contents of your domU's config file?
This is what I changed:
# Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 512)
It was: (dom0-min-mem 256)
Misunderstanding, I was hoping to see the config file of the domU you were trying to create.
You meant this?
[root@gimbli ~]# more /etc/xen/vm03 name = "vm03" uuid = "cc3b0b01-7894-4ac2-06e6-a1a1307939fc" maxmem = 512 memory = 512 vcpus = 1 bootloader = "/usr/bin/pygrub" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ ] disk = [ "tap:aio:/home/vm/vm03.img,xvda,w" ] vif = [ "mac=00:16:3e:0a:13:9d,bridge=xenbr0" ]
Also is this a workstation with Xen domU's for testing/development or a full blown Xen server for running production VMs?
-Ross
This will be a full blown Xen server for production purposes. It will run max 8 Xen guests with cPanel on each one.
In that case if you don't want to shell out the $ for Xen Enterprise I would do these steps for setting up a Xen server:
- for each server, minimal install, no X to reduce any possible dom0
issues, and to allow you to minimize dom0 memory usage, you can then run in 256MB with no X windows!
- use the Xen 3.2 packages off of xen.org, compiled 64-bit, compile on
separate 64-bit platform as the compilation will pull in a lot of other development packages and X. These packages use the Xen kernel from CentOS for the kernel image, and that package comes with the 3.1 Xen image so you'll need to edit the grub.conf to make sure the Xen 3.2 image is used instead of the 3.1 image every time you upgrade the kernel. These packages provide the latest features and fixes as well as the more capable management tools and API which will become a necessity when you manage from the command line and/or have more then 1 server which eventually you will for scalability, redundancy, etc.
- Start seriously thinking about implementing an iSCSI SAN, your
storage requirements will balloon crazy until your virtualization environment stabilizes, and SANs allows for better storage utilization, scalability and also allows for VM migration from one host to another and are a bitch to migrate to after the fact.
- Build your Xen config files by hand, it's the only way to assure
they are setup properly and the way you want.
Since a Xen environment will be sensitive to change, maybe not as much as a LAMP environment, but still probably second to, you may want to manage your Xen build yourself, at least for the servers, as Redhat's Xen implementation is still evolving.
I would use Redhat's Xen environments once they have a pure Xen 3.2 build, as their current Frankenstein environment is really aimed at workstation deployments, especially their hoaky X tool.
-Ross
Ross, you're talking about "scary" new stuff which I haven't even though about. - What I'd like to accomplish, is to have a few dedicated servers (Our company is the hosting company, and this is the first time we go into virtualization ), each running up to say 10 VPS / VM's (which is much cheaper than a full blown dedi to the client) None of the servers have X (no point to it), and we use a very, very minimal install (I don't even have FTP running, since cPanel will provide this). The VPS's will either have 256MB (cPanel minimum) / 512 / 786 / 1GB RAM - Obviously if more RAM is desired per VPS, less will be run on 1 server, or the server will have more RAM & CPU's HDD space will also either be 10 / 20 / 40 / 60 GB per VPS. The VPS' itself will only run cPanel, no X - a server doesn't need X for anything. So, 10 VPS with 512MB each = 12GB needed on host server. Many Xeon mobo's can take upto 32GB RAM.
- I'm a bit sceptic about using Xen 3.2 off the Xen site, as I don't know how well it'll perform on CentOS and I believe that if CentOS hasn't included in their repositories yet, then there must be a good reason. I'll test it on a test server though to see what happens. I think the other problem I have, is that these servers are deployed from the standard CentOS 5.1 CD & a kickstart file with only the necessary software & nothing more. Having to compile software on another machine isn't fun for me.
- I just want to understand this better. If I run a 64bit host, and want to install any other guest (preferably 32bit), then I need to use the "fully virtualized guest" and not the para-virtualized option, right?
- I like where you're heading with the suggestion of an iSCSI SAN, but that's totally new to me as well, and not in my budget right now. Maybe later on when this whole project takes off as I hope for it to take off. But, since you mention it, do you then setup the server with a base OS, and mount the iSCSI SAN as added storage? And then all the VM's get's stored on the SAN, instead of the server's HDD's? And how well will such a setup perform if I have say 5 / 10 servers connected to it? I guess the SAN will then at least need 4 Gigabit NIC's, as the hubs in the DC are only 100Mbit hubs. For a startup SAN, what would you suggest? I guess a PC / server based SAN (in other words, I take a Xeon mobo with plenty of HDD ports and put plenty HDD's on it) isn't really an option?
For now I'm going to manage the Xen stuff myself, I don't have anyone capable of doing this kind of work yet.
-
Ross S. W. Walker -
Rudi Ahlers