Re: [CentOS-virt] Has anyone been able to start a Fedora 16 VM in Xen PV?
On Tue, Jan 10, 2012 at 05:59:56PM +0400, Eugene Chupriyanov wrote:
I've managed to setup F16 PV-guest domU under Xen Cloud Platform. It's
more than just Xen, but solution will be the same.
So what you need to do:
1) Don;t use GPT (install with nogpt kernel parameter)
2) Create bootable /boot partition using ext2 filesystem
3) pygrub looks for grub.cfg in /boot/grub directory (to be exact in
/grub on /boot fs). But in F16 grub is located ion /boot/grub2.
So I just copied grub.cfg from /boot/grub2 to /boot/grub. Maybe there is
a better way to keep up-to-date copy of grub.cfg in /boot/grub.
4) pygrub bootloader fails on following line in default grub.cfg:
set default=${saved_entry}
so I've replaced it with:
set default=0
That should be enough to make f16 to run in PV mode.
Yes, thanks for that! This works for me. How did you know that pygrub
failed on that line?
Anyway, my steps to get F16 going under Centos 5.7 with
xen-3.0.3-132.el5_7.2 were:
1. Create a new PV guest and boot the F16 install image with the nogpt
kernel parameter.
2. After install has finished and before you reboot,
switch to text console on ALT-F2 of your install and copy the
/mnt/sysimage/boot/grub2/grub.cfg to /mnt/sysimage/boot/grub/grub.cfg
and edit the line:
set default=${saved_entry}
to
set default=0
And that's it. The F16 should boot now. The only difference to Eugene's
steps is that I didn't worry about the ext2 boot partition. Mine is
ext4.
Also note that the copy and edit in step 2 should be easy to put in a
kickstart file.
If you forget to do step 2, you can do it on the host with, in my case,
kpartx, mount, and edit the files there. Remember to do a:
echo 1 /proc/sys/vm/drop_caches
so that pygrub will read to changes and not use the cached version.
And finally, when xen-3.0.3-135 is released, it should fix this problem.
I also had success with doing an F15 install, doing an upgrade to F16
and not updating the boot loader. I then manually created a grub.cfg
file. After that F16 booted OK.
I did not try R P Herrold's solution of using an F15 install, installing
fedora-release-16-1.noarch.rpm with rpm, then doing a yum update.
Thanks all you your help.
--
Norman Gaywood, Computer Systems Officer
University of New England, Armidale, NSW 2351, Australia
ngayw...@une.edu.auPhone: +61 (0)2 6773 3337
http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Has anyone been able to start a Fedora 16 VM in Xen PV?
Sorry for the top post but I think it's appropriate here. The message below was posted 20th of December last year with no response. I've now hit the same problem. I have CentOS 5.7 and and trying to install an F16 domU PV guest. It seems that pygrub is failing to read the grub2 setup. It also seems that there is a fix for this in xen-3.0.3-135.el according to: https://bugzilla.redhat.com/show_bug.cgi?id=746602 (pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1) However, centos only has xen-3.0.3-132.el5_7.2 and so does not have the pygrub fixes and I'm not even sure RH has relased xen-3.0.3-135.el yet. Has anyone found a way to install F16 as a domU guest on Centos 5.7? On 20 December 2011 00:33, Scot P. Floess sflo...@nc.rr.com wrote: All, I've had a heck of a time getting Fedora 16 to run as a guest VM under CentOS 5.7 host as a paravirtualized Xen guest. I believe the issue has something to do with Fedora 16 using grub2... When I attempt to start the VM (via xm create), I get this error: Using config file /etc/xen/fedora-workstation. Traceback (most recent call last): File /usr/bin/pygrub, line 686, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger xend Error: Boot loader didn't return any data! In my kickstart, I had to create a partition for F16 as: part biosboot --fstype=biosboot --size=1 I didn't readily find the error when googling... Has anyone been able to run F16 as a PV guest? And if so, what did you do to make it happen? Thanks! Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.au Phone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~norm Fax: +61 (0)2 6773 3312 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Has anyone been able to start a Fedora 16 VM in Xen PV?
On Mon, Jan 09, 2012 at 07:20:05PM -0500, S.Tindall wrote: On Mon, 2012-01-09 at 18:56 -0500, R P Herrold wrote: On Tue, 10 Jan 2012, Norman Gaywood wrote: https://bugzilla.redhat.com/show_bug.cgi?id=746602 (pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1) why would one use GPT for a domU? seems like gross overkill There are a bunch of grub2-related issues associated with F16 anaconda and one of the easiest ways to deal with them is to use gpt. There is a nogpt kernel option that may help, but I have not tried it. Yes, GPT is the default for F16 so it is easier just to go with it. I have tried the nogpt option and F16 installs OK (as it does without it). However it still can't boot: [root@dom0 ~]# sfdisk -d /dev/VM/f16 # partition table of /dev/VM/f16 unit: sectors /dev/VM/f161 : start= 2048, size= 1024000, Id=83, bootable /dev/VM/f162 : start= 1026048, size= 40916992, Id=8e /dev/VM/f163 : start=0, size=0, Id= 0 /dev/VM/f164 : start=0, size=0, Id= 0 [root@dom0 ~]# pygrub -i /dev/VM/f16 Traceback (most recent call last): File /usr/bin/pygrub, line 691, in ? chosencfg = run_grub(file, entry, fs) File /usr/bin/pygrub, line 545, in run_grub g = Grub(file, fs) File /usr/bin/pygrub, line 203, in __init__ self.read_config(file, fs) File /usr/bin/pygrub, line 402, in read_config if self.cf.filename is None: AttributeError: Grub instance has no attribute 'cf' The error is in the parsing of the grub2 config I believe. -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] More than 32G on memory in a domU guest?
Hmm bad form to answer myself, but: On Wed, Jun 29, 2011 at 09:41:18AM +1000, Norman Gaywood wrote: dom0# cat /etc/xen/turing ... maxmem = 4 memory = 4 dom0# xm list ... turing 1412 r- 1842736.7 guest boots like this (from /etc/grub.conf of guest): title Fedora (2.6.35.13-92.fc14.x86_64) However, the guest reports this: domU# grep MemTotal /proc/meminfo MemTotal: 32870604 kB I missed this in /usr/src/kernels/2.6.35.13-92.fc14.x86_64/.config CONFIG_PARAVIRT_GUEST=y CONFIG_XEN=y CONFIG_XEN_MAX_DOMAIN_MEMORY=32 So I guess that means that the fedora kernels are not built to use more than 32G of memory in DomU. -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS] adding user ldif to ldap
On 29 October 2010 10:39, Tim Dunphy bluethu...@gmail.com wrote: LDAP# ldapadd -x -D cn=Manager,dc=summitnjhome,dc=com -W -f /tmp/passwd.ldif adding new entry uid=root,ou=People,dc=summitnjhome,dc=com ldap_add: Invalid syntax (21) additional info: objectClass: value #6 invalid per syntax Here is the first entry which presented a problem when I attempted to add it: dn: uid=root,ou=People,dc=summitnjhome,dc=com uid: root cn: Enoch givenName: Enoch sn: mail: r...@summitnjhome.com mailRoutingAddress: r...@mail.summitnjhome.com Perhaps the 6th line of attributes (value #6?) contains mailRoutingAddress. Is mailRoutingAddress defined in your schema? -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.au Phone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~norm Fax: +61 (0)2 6773 3312 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-virt] RHEL 5.5 Xen fixes
On Wed, Mar 31, 2010 at 11:28:56PM +0300, Pasi Kärkkäinen wrote: On Wed, Mar 31, 2010 at 03:43:38PM -0400, Grant McWilliams wrote: Are these changes in the kernel or changes to the installed Xen? I'm wondering if this effects anyone using Xen 3.4 or newer. I think they're mixed.. you need to go through the bugzillas to figure out. (and possibly compare to the kernel changelog above). This may be a dumb/FA question but how do you run Xen 3.4+ with the latest Centos kernel? Are there centos/redhat kernels rebuilt with newer Xen or do you have to do this yourself? I see source for kernel 2.6.18 with Xen 3.4 here: http://www.xen.org/products/xen_source.html but that kernel does not have all the fixes that have gone into the RH/Centos 2.6.18 kernel. -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] reboot guest on panic
Thanks Pasi. On Sun, Mar 14, 2010 at 03:16:13PM +0200, Pasi Kärkkäinen wrote: On Sun, Mar 14, 2010 at 09:03:23AM +1100, Norman Gaywood wrote: I have a guest that keeps crashing and want to automatically reboot it when it crashes. See: xen PV guest kernel 2.6.32 processes lock up in D state https://bugzilla.redhat.com/show_bug.cgi?id=550724 if you want to look at the details on the crashing. Btw please see: http://wiki.xensource.com/xenwiki/XenCommonProblems Especially the chapter about debugging crashed guests. It would be very helpful to grab a stacktrace of the crashed guest to debug it. I've already done this, there are some stack traces in the bugzilla entry. Andrew Jones seems to think that the problem in this case is actually in the Xen hypervisor and not the guest. Problem is I seem to be the only one hitting this. Redhat bugzilla seems to be down, so I can't check the details about the bugreport. Is the guest single-vcpu or multi-vcpu? 32bit or 64bit? 64bit multi-vcpu. The guest is quite heavyweight, 30GB of memory and 12vcpu. It's a LTSP server designed to handle lots of graphical logins for computer science students. This, I guess is not a common workload. -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] reboot guest on panic
Thanks Dan, On Sun, Mar 14, 2010 at 05:06:32PM -0400, Dan Hrabarchuk wrote: Try this in the guest: echo 1 /proc/sys/kernel/panic_on_oops This might be a bit too much. There is another harmless oops that occasionally happens related to ext4 quotas. I wouldn't want it to reboot on those. The hung_task_panic=1 does in fact cause the panic when I want it. However the problem seems to be that it does not reboot after the panic. echo 5 /proc/sys/kernel/panic I already have this, although I have a value of 15. On 03/13/2010 05:03 PM, Norman Gaywood wrote: I have a guest that keeps crashing and want to automatically reboot it when it crashes. See: xen PV guest kernel 2.6.32 processes lock up in D state https://bugzilla.redhat.com/show_bug.cgi?id=550724 if you want to look at the details on the crashing. Anyway, I boot the guest with the kernel command line parameter: hung_task_panic=1 I have kernel.panic = 15 in the guest /etc/sysctl.conf In the guest config file in dom0 I have: on_poweroff = destroy on_reboot = restart on_crash = restart The guest manages to panic when it detects the hung tasks and I get this on the guest console: Kernel panic - not syncing: hung_task: blocked tasks Rebooting in 15 seconds.. However, it never restarts. It just hangs around until I do a xm destroyguest xm createguest Have I missed something? -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] reboot guest on panic
On 15 March 2010 10:12, Christopher G. Stach II c...@ldsys.net wrote: - Norman Gaywood ngayw...@une.edu.au wrote: 64bit multi-vcpu. The guest is quite heavyweight, 30GB of memory and 12vcpu. It's a LTSP server designed to handle lots of graphical logins for computer science students. This, I guess is not a common workload. I wouldn't say that it's an uncommon workload, or VM configuration, at all. However, it is an uncommon kernel. Is there any reason that you need to use that one? Can/Does it work with something more approved? LTSP setups are either Fedora or Ubuntu which run about the same vintage of kernel. Thing is that the 2.6.3? kernels that are supposed to work as a Xen PV guest have been around a long time now. None of them seem to work in my case. The oldest I tried was 2.6.30. Installing say a Centos kernel on fedora does not look to be an option. Ubuntu seem to have pretty much the same software/kernel as fedora. It's a lot of work to build sometime like our current setup on Ubuntu only to discover it probably has the same problem. Note also this problem was not reproduced in testing until very recently (see the bugzilla). Another way would be to install Fedora/Ubuntu on the bare metal like we have on older versions of this system. But sigh, I hit a different bug going that way with Enterprise Hardware not supported in modern kernels. So these 2.6.3? kernels are supposed to work as PV guests. And in any event, it looks like the problem might be in the Xen Hypervisor anyway. The bugzilla was moved from a Fedora bug the a RH EL bug (not by me). My thinking at the moment for a way forward is to look at switching my guest to KVM. But that's even more bleeding edge. -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] reboot guest on panic
On Sun, Mar 14, 2010 at 07:33:43PM -0500, Christopher G. Stach II wrote: - Norman Gaywood ngayw...@une.edu.au wrote: LTSP setups are either Fedora or Ubuntu which run about the same vintage of kernel. There isn't a whole lot special happening on the server side for LTSP. [deleted fine description of basic LTSP requirements] Actually we already have the LTSP basic server requirements separated out and running on bare metal. As you say, there is not much to do here. The unstable VM is running the desktops for the LTSP. Also a lightly loaded httpd and a lightly loaded samba server. There is also a light load of NFS which I have almost disabled while this problem persists. Now, if you want something specific to a recent Fedora version on the server, then you're just asking for trouble. Well yes, seems I've hit trouble this time. Was expecting some trouble with the desktop apps and was happy to deal with that. I was not expecting significant kernel trouble however. Rebuilding a modern desktop distro with an older kernel is a lot of work. That's what distributions are for right? -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] reboot guest on panic
I have a guest that keeps crashing and want to automatically reboot it when it crashes. See: xen PV guest kernel 2.6.32 processes lock up in D state https://bugzilla.redhat.com/show_bug.cgi?id=550724 if you want to look at the details on the crashing. Anyway, I boot the guest with the kernel command line parameter: hung_task_panic=1 I have kernel.panic = 15 in the guest /etc/sysctl.conf In the guest config file in dom0 I have: on_poweroff = destroy on_reboot = restart on_crash = restart The guest manages to panic when it detects the hung tasks and I get this on the guest console: Kernel panic - not syncing: hung_task: blocked tasks Rebooting in 15 seconds.. However, it never restarts. It just hangs around until I do a xm destroy guest xm create guest Have I missed something? -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] reboot guest on panic
On Sat, Mar 13, 2010 at 10:21:14PM -0600, Christopher G. Stach II wrote: - Norman Gaywood ngayw...@une.edu.au wrote: I have a guest that keeps crashing and want to automatically reboot it when it crashes. See: xen PV guest kernel 2.6.32 processes lock up in D state https://bugzilla.redhat.com/show_bug.cgi?id=550724 if you want to look at the details on the crashing. If your guest's state is corrupted, you can't rely on its behavior. For that reason, you should set up a watchdog and only rely on the panic behavior as a preliminary measure. I figured that I had setup a watchdog with the hung_task_panic=1 guest parameter. Is there another way of setting up a watchdog in this case? -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngayw...@une.edu.auPhone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~normFax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
