similar to: PVGrub can''t find config file for domU on logical volume

I''ve been using lvm under centos to create the backing store for domUs and although the performance seems acceptable it has some shortcomings. The biggest of which is the LVM bug which prevents me from removing an lv (it says it is still mounted and it definitely isnt). I thought this was just a centos bug but it appears to be evident in debian and ubuntu too and I really can''t

so it appears that PVGRUB requires that I specifiy (in my domain config file) either the -x86_64 or the -x86_32 version. Does anyone have a clever way I can let my users switch between x86_64 and i386 without giving them access to the domain config file? Preferably, something more secure than PyGRUB? I was considering hacking up PyGRUB so that it only allows the user a choice of

Hello I''m trying to convert a HVM to PV dom0. The domU is a 10SP2 SLED ( Kernel 2.6.16.60-0.21 i386) and is a SLES11SP2 dom0 (Kernel 3.0.13-0.27-xen 64bit). The truth is that every tutorial I see it differently and I do not know where this error. When I start the domU, pvgrub shows the options but when I select the kenel-xen, returns the error "Boot loader did not return any

Hello, The attached patch adds bzip2 and lzma/xz libs to stubdom for pvgrub. This is the first step of getting the additional compression methods supported in pvgrub. There''s still some Makefile voodoo to sort out before pvgrub actually properly gets linked against these new libs. This patch only adds the libs and makes them build. -- Pasi

Distro: debian unstable Xen version: 4.0.0-2 This is the config: #HVM #still no qemu-dm in debian #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = ''hvm'' #memory = 2048 #name = "webserver" #vif = [''bridge=eth0''] #disk = [''tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w'',''phy:/dev/cdrom,xvdb:cdrom,r'']

Hi, Having a problem getting a domu to boot correctly. When I enter xl create guest it boots straight into grubdom. If I enter the config location in grubdom t boots as expected. The location of the grub.cfg is the same in my domu config as what in entering but just will not work. Any ideas? Ian .

Hello, I am still confused: does pyGrub run in dom0 as root? as it says in here: "PyGRUB used to act as a “PV bootloader”: it runs in dom0 as root, opens the PV disk image, reads its GRUB menu.lst, presents a GRUB-like menu to let the user choose a kernel which it copies to the dom0 filesystem, it then closes the disk image and eventually tells the domain builder to use that copy. Such a

Thank Zhigang Wang for your response. I have test pvgrub with this config file: #pv-config kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz" extra = "(hd0,5)/boot/grub/menu.lst" memory = 512 name = "ExampleDomain" disk = [ ''file:/var/lib/xen/images/opensuse11-1/disk0,xvda,w'' ] vif = [ "bridge=eth0" ] root = "/dev/sda5 ro" start

I have this working on Fedora. It turned out to be very easy to add this as I simply took the grub-ext4-support.patch from the Fedora grub package and put it in xen-4.0.1/stubdom/grub.patches/ . Using pvgrub (without a vif on the virtual machine as I was having problems if I did give it a network interface) I could read and boot from ext4 partition with this patch but not without it. Is this

When will we see progress on this? pvgrub is the newer and better thing, and it's the only way to do many things. For one thing, It should make it easier to boot an OS on a partitioned block device, pygrub can't do that unless you probe the paritions first and make then visible on Dom0 - a hassle. Otherwise, it would just simply do what real GRUB can really do. I would really like to

Hi, I test pvgrub on xen-3.3.0. After starting pvgrub with "xm cr xmexample.pv-grub", I can see nothing but qemu window. With "xm li" , I can see this domain is running: Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r-----

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS

Hey all, I have need to boot 32bit domu''s on a amd64 system. I was able to deploy a 32bit image but the kernel is still 64bit. I have a feeling in my .cfg file for the domU I need to specify a 32bit kernel. Is this correct? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, to make transitions more convenient, I've done this by using uuid instead of device names. If you ls -l /dev/disk/by-uuid inside your domU, you'll see something like lrwxrwxrwx 1 root root 10 5. Mai 07:38 39a2a64b-0716-47ad-92f4-a7437cac54ee -> ../../sda2 lrwxrwxrwx 1 root root 10 5. Mai 07:38 e8b97b59-a790-417c-8231-fe8da8b6e6ee -> ../../sda1 In /etc/fstab inside the domU,

On Sat, Feb 20, 2016 at 9:24 PM, Sarah Newman <srn at prgmr.com> wrote: > On 02/17/2016 04:30 AM, George Dunlap wrote: >> I have the following packages going through the CBS: >> * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 >> * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 >> * A CentOS 6 xen-4.4.3-11, with XSAs 170 >> >> All these should show up in

Problems start before any of the kaiser code executes, though it could still be related to CONFIG_KAISER since that has effects beyond kaiser.c. --- (early) Initializing cgroup subsys cpuset (early) Initializing cgroup subsys cpu (early) Linux version 2.6.32-696.18.7.el6.x86_64 (mockbuild at c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Thu Jan 4 17:31:22 UTC

I have a couple Debian 6 HVM VMs. From what I''ve read, Debian 6''s standard kernels have pv_ops already enabled. I''d like to convert these to pv for the following reasons (Assuming both of are valid expectations): 1) so the VMs use pv for the NICs 2) so the VMs properly respond to shutdown/reboot commands from xm I''m having trouble converting them. I believe

Anybody tried to use btrfs on rootfs / in domU with pygrub? I tried and realised that pygrub can''t use btrfs. Workaround is to make /boot outside rootfs, but pygrub search kernel in directory /boot. It can be workaround via softlink on /boot, but... too much workarounds. Distro: debian squeeze + xen 4.0 I wait for yours experiences. Regards, Marcin Kuk

Does this install -d -m0755 -p "/mnt/gen2/TmpDir/portage/app-emulation/xen-pvgrub-4.3.0/image//usr/lib/xen/boot" install -m0644 -p mini-os-x86_32-grub/mini-os.gz "/mnt/gen2/TmpDir/portage/app-emulation/xen-pvgrub-4.3.0/image//usr/lib/xen/boot/pv-grub-x86_32.gz" make: Leaving directory `/mnt/gen2/TmpDir/portage/app-emulation/xen-pvgrub-4.3.0/work/xen-4.3.0/stubdom'