similar to: [PATCH] xen-unstable: Add bzip2 and lzma/xz libs to stubdom for pvgrub

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'

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

parent: 24691:3432abcf9380 tip Fix x86_32 build branch: default commit: 4 modified, 1439 unknown update: (current) /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c: In function âqemu_aio_waitâ: /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:20: error: macro "remove_waiter" requires 2 arguments, but only 1 given /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:5: error: âremove_waiterâ

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 =

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

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

when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file gets corrupted. the same configuration was working ok on low load with xz compression. Dovecot Version 2.2.12 Linux Mint 16 EXT4 Filesystem another dovecot user already reported the same problem on the mailinglist, using dsync. That user switched to bz2 compression what worked for him. the answer was : > are you on

Hi, Would it be possible to ship the releases using xz (or lzma) ? -rw-r--r-- 1 root root 3423720 Jul 20 12:17 syslinux-4.02-pre5.tar.xz -rw-r--r-- 1 root root 3423147 Jul 20 12:17 syslinux-4.02-pre5.tar.lzma -rw-r--r-- 1 root root 4395234 Jul 20 12:17 syslinux-4.02-pre5.tar.bz2 -rw-r--r-- 1 root root 20080640 Jul 20 12:17 syslinux-4.02-pre5.tar Regards, Shantanu

Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> --- stubdom/configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stubdom/configure.ac b/stubdom/configure.ac index db44d4a..384a94a 100644 --- a/stubdom/configure.ac +++ b/stubdom/configure.ac @@ -18,7 +18,7 @@ m4_include([../m4/depends.m4]) # Enable/disable stub domains

The default make targets in the top level makefile set DESTDIR which gets applied when the stubdom makefile tries to do a make install within gmp to install libgmp.a to the cross root. Ian, do you want to apply this to your tree and commit the whole thing or would you prefer I roll out a fresh new patch set with all updates applied? Signed-off-by: Matthew Fioravante

I test stubdom in xen-3.3.1, when I start it, just see the message bellow using "xm li" . It seems stubdom haven''t start. Name ID Mem VCPUs State Time(s) Domain-0 0 964 2 r----- 34.8 hvmachine 1 1024 1 ------ 0.0 the two config

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

Hi, Since c/s 18372, building stubdom fails with: cc1: warnings being treated as errors lib/sys.c: In function ''munmap'': lib/sys.c:1182: warning: pointer of type ''void *'' used in arithmetic make[2]: *** [/xen/xen-unstable.hg/stubdom/mini-os-x86_64-grub/lib/sys.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: *** wait: No child processes.

While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12 (compiled from source) dsync aborts with a backtrace on some (maybe 15 out of 800) mail accounts: (same error happens wiht or without -f flag) dsync -D -v -o mail_fsync=never mirror -f -R -u user at domain imapc: <snip> dsync(user at domain.com): Debug: brain M: in state=sync_mails dsync(user at domain.com): Debug: brain M:

Hi, Do the gplpv drivers work with stubdom? I''ve tried to get them working and posted to the mailing list for help but the only reply I got was a suggestion to use config settings which appear to allow the gplpv drivers to access the hd at the same time as the stubdom, which might work but isnt what I was after, have I misunderstood stubdom and there is no advantage to using gplpv

This patch ports 5 new applications to the stubdom makefile structure for inclusion into stubdom domains. While these are required for vtpm-stubdom and vtpmmgrdom they could be used with other stubdom applications. -libgmp 4.3.2 -openssl 1.0.0a -polarssl 0.12.1 -berlios tpm_emulator 0.6.1 -vtpm_manager (from the tools directory) Signed off by: Matthew Fioravante

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1341839122 -7200 # Node ID 2dd50c201ca0d3542f3589942ae9e51d33ec7509 # Parent 42f76d536b116d2ebad1b6705ae51ecd171d2581 stubdom: fix errors in newlib rpmlint found a few code bugs in newlib, and marks them as errors after rpm build. Add another newlib patch and apply it during stubdom build. I: A function uses 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

After syncing to the latest xen-unstable sources, I am getting following compilation error : make[3]: *** No rule to make target `/data/xen-sources/xen-unstable.hg/stubdom/ioemu/i386-stubdom/qemu.a'', needed by `/data/xen-sources/xen-unstable.hg/stubdom/mini-os-x86_32-ioemu/mini-os_app.o''. Stop. make[3]: Leaving directory

Having fs-backend running in background, tried to start:- root@ServerXen331:/etc/xen# cat f10.hvm-stubdom kernel = "/usr/lib/xen/boot/hvmloader" builder="hvm" memory = 1024 name = "f10.hvm" disk = [ ''phy:/dev/sdb11,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r'' ] vif = [ ''type=ioemu, bridge=eth0'' ] device_model =