similar to: PV Grub Questions

Hi folks PV-GRUB built from Xen 3.3.0 is not able to read from devices without a partition table: | grubdom> root (hd0) | Filesystem type unknown, using whole disk Part of the config: | disk = [ "phy:vg0_sledgehammer/servext_root,xvda,w" ] Device: | # file -s /dev/vg0_sledgehammer/servext_root | /dev/vg0_sledgehammer/servext_root: symbolic link to

Hello all Xen devels, I''m writing howto''s in brazilian portuguese language about Xen-3.3.0 stubdom, pv-grub and others configurations. Following what is written in xen-3.3.0/stubdom/README, I tried start a HVM but without success. When I start the virtual machine calling ''xm create hvmtest'' command, in a few seconds the virtual machine is dead (see

Hello all, I''ve patched pv-grub to allow it to boot a Solaris PV domU using an unmodified menu.lst. The attached patch has been tested with various Solaris versions (Solaris 11 Express, OpenIndiana 151a, OpenSolaris 134, Nexenta Core 3.0.1; all 64-bit). I appreciate your feedback. The patch consists mainly of Oracle''s grub modifications, which add ZFS support and

Add a couple of documentation details about PV-GRUB support - the menu.lst content can be passed as a ramdisk. - virtual partitions are not supported. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> diff -r b8d2a4134a68 stubdom/README --- a/stubdom/README Wed Mar 03 17:41:58 2010 +0000 +++ b/stubdom/README Wed Mar 03 20:42:53 2010 +0100 @@ -52,11 +52,17 @@ extra =

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'

samuel, I have a try with HVM stubdomain on r17062, but failed to make on 32b platform. Attached patch can fix it, but don''t know if okay. After installation, I failed to start stubdom. So I created it manually and got following debug mesg(both HVMdomain and stubdom are created) Can you give some lights on following questions: 1. I use default vnclisten. Does it matter? 2. Seems qemu

PV-GRUB: xfs support i386 doesn''t have PAE anyway. Index: fsys_xfs.c =================================================================== RCS file: /sources/grub/grub/stage2/fsys_xfs.c,v retrieving revision 1.5 diff -u -p -r1.5 fsys_xfs.c --- fsys_xfs.c 8 May 2005 02:18:14 -0000 1.5 +++ fsys_xfs.c 10 Jul 2008 13:09:50 -0000 @@ -101,7 +101,7 @@ static inline __const__ xfs_uint16_t le16

Hello, When statically linking the following program: #include <stdio.h> #include <xenctrl.h> #include <xenguest.h> int main(void) { printf("%p\n", xc_domain_resume); printf("%p\n", xc_domain_save); return 0; } gcc -static test.c -o test -lxenguest -lxenctrl -lpthread -lz we get

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

hi all, i want to install xen3.1 on my system, suse linux enterprise server 10 SP1 (kernel 2.6.16.46-0.12). i download the tarball binary file. it contains only "vmlinuz-2.6.18-xen" and "xen-3.1.gz", no initrd. but see the following code in my grub menu.lst, it seems like i need the initrd file. i tried the installation with this binary Tarball, it didn''t work.

stubdom: int32_t is provided by stdint.h, not sys/types.h diff -r c2472ded5c7c extras/mini-os/include/posix/dirent.h --- a/extras/mini-os/include/posix/dirent.h Tue Aug 26 15:16:57 2008 +0100 +++ b/extras/mini-os/include/posix/dirent.h Tue Aug 26 16:43:27 2008 +0100 @@ -1,7 +1,7 @@ #ifndef _POSIX_DIRENT_H #define _POSIX_DIRENT_H -#include <sys/types.h> +#include <stdint.h>

Hi, Let me start a new thread for this. I contacted the Grub people, and they seem more interested in creating a native Xen port of Grub than piggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources?

Hi, Let me start a new thread for this. I contacted the Grub people, and they seem more interested in creating a native Xen port of Grub than piggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources?

Hi All, I want to test REMUS over XEN, I would like to know the basic steps to be followed . I have installed xen4.1 on debian and i didn''t find any command related to remus, is there any steps which i have to carry out? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, List, In checking the page fault problem when using pv-grub to start domU in opensuse12.3[1], found that the problem is caused by ''-fstack-protector'' flag which is introduced in rpm build: export EXTRA_CFLAGS_XEN_TOOLS="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_TRADITIONAL="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_XEN="$RPM_OPT_FLAGS" with

Greetings! Trying to to run a xen3 domU on a xen4 dem0 I run into problems. The xen server ''XEN1''(dom0) is openSUSE-11.3 (kernel 2.6.34) and xen-4.0.1. With qemu I created an image ''M08.raw'' from the SUSE-9.3 (kernel 2.6.11) and XEN-3.0 installation CD''s. The XEN modules were included in the installation. In M08.raw/boot I configured grub/menu.lst:

Hi all, I have been having an issue for over a year with several Xen installations and have not been able to find out if this is just something I am missing. Basically I am trying to configure a firewall with two ethernet cards in a domU using pci passthrough. I am hiding the Ethernet cards at boot time via the pciback.hide kernel option. Right now I am running Xen 3.3.0 and the two Ethernet

I just downloaded Xen-4.1.1 from xen.org, compiled it, and installed it. I then compiled kernel 3.0.0 and added the hypervisor and dom0 kernel in a grub 2 entry. After booting, I executed "xl list," to confirm the hypervisor was running. I was greeted with this message: libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such

After hours of googling and not really finding a definitive solution to my problem, I''m a little stuck and would really appreciate some help from others. I have a CentOS 5.4 x86-64 server running Xen 3.3 from the gitco repos as dom0. On this I have created two logical volumes comprising 8GB for the system disk (xvda) and 1.5GB for swap (xvdb). I ran mkfs.ext3 and mkswap on these to

Hi, I have an Slackware 12.1 running on Intel Core2Quad, 4 Gb RAM. (The result of dmesg is attached on this e-mail) I have downloaded ''Xen 3.3.0 official source distribution tarball'' from www.xen.org. Run make world, make install. Have no errors. Installed GRUB correctly and added the following lines on menu.list: title Xen 3.3 root (hd0,1) kernel /xen.gz dom0_mem = 262144