similar to: modelling domU bootloaders

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something

domUloader potentially makes my life a lot easier, but from experiments and looking at the code, it doesn''t seem like there is any way to pass kernel command line arguments with it. Am I just missing something? Thanks, John Byrne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi: Reading Red Hat's Website and a printed manual of RH184 (Red Hat Virtualization course) I see that RHEL 5 only supports RHEL 4.5 and RHEL 5 as paravirtualized guests. So I asume this is the same situation for CentOS 5, right? What's the dependency between Xen versions for paravirtualized guests? I ask this questions because I got this experiences: 1. Running CentOS 5 as Dom0 - RHEL

Hi all Xapian-devel, Gist: https://gist.github.com/10d2222d8bffe8d7631d I'm using Xapian-TermGenerator to extract Norwegian sentences to vsm (vector space model) using TermGenerator. But when I test generating vsm from 'Truet med ? stevne misforn?yd PC-kunde - PC-leverand?ren Asus likte sv?rt d?rlig kundens misforn?yde leserbrev.' It doen't return 'asus' result in vsm.

Hi: Reading Red Hat''s Website and a printed manual of RH184 (Red Hat Virtualization course) I see that RHEL 5 only supports RHEL 4.5 and RHEL 5 as paravirtualized guests. So I asume this is the same situation for CentOS 5, right? What''s the dependency between Xen versions for paravirtualized guests? I ask this questions because I got this experiences: 1. Running CentOS 5 as

Package: xen-utils-4.4 Version: 4.4.1-9+deb8u8 Severity: normal Under Xen 4.1 in Debian 7 (wheezy), the following works when included in a DomU configuration in "/etc/xen/cfg/" -- bootloader = '/usr/lib/xen-default/bin/pygrub' After upgrading to Xen 4.4 as part of an upgrade to Debian 8 (jessie), the DomU silently fails to start. Examination of the log files shows that the

Hi, I have a Xen server running OpenSuSE 10.2, with Xen version 3.0.3_11774. It''s happily hosting two DomU''s running the same OS / kernel. Now I tried to create a new DomU running a newer OS - OpenSuSE 11.1. It comes with Xen version 3.3.1_18494_03. Unfortunately for me, it doesn''t work - this is what I get: > xen1:/etc/xen/vm # xm create NEW > Using config file

Yesterday, I had a PV OpenSolaris DomU stop responding. I looked on my xen machine and it was in a paused state. I ended up destroying it and then doing xm create to bring it back up. It won''t boot, and I think PyGrub is hanging. Not sure how to resolve this, there aren''t any errors being presented in xen/xm itself. If I try ''xm create config.conf'' it just

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

This is a proposal for modifying the interface for domU bootloaders (i.e. something that provides us with a kernel and ramdisk file with which the domain can be booted). The current interface, as is, has a number of problems, including: 1) the first disk specified is assumed to be the disk containing the files 2) ''bootentry'' is highly pygrub-specific. There is no easy facility

Thanks in advance for your patience and assistance. Since a system administrator's work is most successful when nobody knows you've done anything....(ugly that...you get neither raises nor equipment funding as a result), I prefer to learn from other's experiences rather than fail in the same pits. We are considering a switch from UW to Dovecot, since our users persist in using

Hi, how can I install a openSuSE 10.3 PV-guest on a LVM-drive of a openSuSE 10.3 host with Xen 3.10? On 10.2 with Xen 3.0.3 the openSuSE-YaST-module for managing VMs could install the system also on block-devices, unfortunately this is not possible anymore with OSS 10.3 :-( What I have tried: - I created two LVM-partitions, one for "/" one for swap. - Installing an OSS 10.2 PV-guest

Doing a kickstart install of Fedora 12 results in a non-bootable image. >From a virt-maanger instance, the error produced when trying to run the domU is: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 498, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup

I have a sles10 domU running on a sles11 dom0. xen is version 3.4. We''re trying to pass through a scsi card to the domU. We assign the domU the scsi card through virt manager. When we try to boot the domU it won''t boot. We need to update fstab and menu.lst, but we need to boot with the hardware attached to see how it''s being seen by the domU. On a physical machine we

I''ve done something apparently, but can''t for the life of me figure out what. Perhaps someone can help: I have an LVM based domU which has been working without problem for weeks. I made some final changes to it last week, shut it down and ran the following to create a backup image: dd if=/dev/VolGroup00/wspd of=mail2.img bs=1M At least this is the only thing I can

Hi, I have a host with 6 VMs set to autostart. When this host reboots, it starts libvirtd, pegasus cimom and libvirt-cim. It also restarts the VMs. Intermittently we noticed a core during start up that points to the last call made by libvirt-cim to "virInitialize". I am thinking that it is a timing issue where virInitialize is called while libvirt is trying to autostart the VMs.

Hi, currently i am using KVM, but i want to switch (back) to xen. All my VMs have a own partition inside a lvm. Inside of this partition are 2-3 own pratition. if i want to access them, i can do this by "kpartx -a /dev/vg/VM". Usually my domu configs look like this: bootloader=''/usr/bin/pygrub'' name="ipfire" memory=512 acpi=1 apic=1

Hello, I have a small Xen farm of 8 dom0 servers with 64 virtual machines running para-virtualized and this has been working great. Unfortunately, I''ve hit a limit: my iSCSI hardware supports only 512 concurrent connections and so I''m pretty much at the limit. (Wish I would have seen that problem sooner!) Of course, 87% of those connections are idle-- but necessary because I

I have fedora13 as domain0 kernel on xen-3.4.3 or xen-4.0.1. I installed ubuntu10.04 as guest-os following this : 1) download installer from : - http://fi.archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz - http://fi.archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz to /boot directory 2) edit xen guest