search for: bootentri

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

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

I could use some help trying to recover VMs on a system that used to run xen-3.0.0 under sarge. The host (Domain0) bit the dust, so I rebuilt it using SUSE Linux 10.1 which has xen-3.0.2-2 packages. xend is running and I can do xm list, xm info and so on. It still sees the LVM volume groups that the VM data resides on. My VMs are sitting on /dev/vg20/vol01, /dev/vg20/vol03 .... Because I lost

I am having issues with guest OSes running on SLES10 (Sun 4200) hosts. Periodically, the guest OS system drops off the network. From the general network it is not pingable, consequently, ssh fails. If however, I log into the SLES10 server that is hosting the guest OS and ssh to the guest OS, then it becomes immediately pingable and accessible to the rest of the network. Almost like the

Hi, in SLES10 YaST insists in "xorg-x11" being installed, even if the display is redirected to a remote host. So I thought: Can''t I do it simpler? I''m still new to XEN, but I started like this: mount the SLES10 DVD to /mnt, and use this configuration file: ----- disk = [ ''phy:/dev/system/as1,hda,w'', ''phy:/dev/hda,hdb,r'' ] memory

I have installed the 210 gplpv (debug), when I try to update them with current gplpv I get a BSOD even so when I try to uninstall them. Now I have made a bootentry that specifies NOGPLPV, what gives me a bootable system after such a crash, I found (uninstalling the leftover driver packages after getting bsod during uninstall of the main package) that uninstalling the net driver leads to bsod. Now

Xen Host Server OS: SLES10 Kernel: 2.6.16.21-0.8-xen x86_64 Hardware: Sun 4200 Memory: 12Gb Guest Domains (2 total) RHEL4-U3 2.6.16-xen x86_64 2Gb Swap 4Gb RAM 2 Nics bridged to seperate physical Nics (Public and Private) Systems come up normal and we are able to mount filer space to the guest domains and do work. However, at some point, the guest

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

Hello, We''re running Xen Unstable changeset 15468 with SLES10 on a Unisys ES7000/one 56x cpu and 160GB memory. Xen is built with NR_DYNIRQS=1024 and max_phys_cpus=64, and booted with dom0_mem=1024 and xenheap_megabytes=64. We have 320 para-virtualized SLES10 VMs on external storage. Our script starts a VM, waits for the start to complete, then starts the next: "for i in *.cfg;

Greetings! I finally got the install done for a couple of gust OSs (Win 2003 server & Suse Enterprise 10) Bothe gusts are up and running, but - no networking. My setup: Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 onboard GB NICs Host OS- Suse Linux Enterprise server 10 Xen - 3.0.2_09749-0.4 Config file for Win 2003 server guest: # -*- mode: python; -*-

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

Suse 10.1 AMD64 Xen3 New to Xen. The dom0 is up and running. I am trying to get my first domU working. My approach is to use precompiled images from jailtime.org. After some manual tinkering with the .cfg file the domU proceeds to boot but stalls with the following error. I cannot get past this - any ideas ? Brian Using config file "/etc/xen/vm/vm1". Started domain vm1 Bootdata ok