similar to: Opensolaris domU - install ok, pygrub boot not ok.

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

I am trying to install CentOS from an ISO image file but the installer does not see a CD-ROM drive. The VNC viewer works but the CentOS installer indicates "Unable to find any devices of the type needed for this installation type." Then it prompts with "[Select driver] [Use a driver disk] [Back]". I have tried several variations of the "disk" paramater, all

>That is, I think the following config should work on those Ubuntu >systems > PYTHON=python > PYTHON_PREFIX_ARG='''' >although you may need to do > PREFIX=/usr/local >too. # make tools fails on Ubuntu 9.04 Server with Config.mk suggested above This one Config.mk (untouched) works fine:- PYTHON ?= python PYTHON_PREFIX_ARG ?=

Yes, build issue has been resolved perfectly by Changeset 19594. However, NO  hotplug logs again. root@ServerJaunty:/var/log/xen# ls -l total 788 -rw-r--r-- 1 root root 184025 2009-05-15 11:12 domain-builder-ng.log -rw-r--r-- 1 root root 157480 2009-05-15 11:09 xend-debug.log -rw-r--r-- 1 root root 446867 2009-05-15 11:14 xend.log I''ve also made same test on F11 preview ( obviously not

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file "/etc/xen/squeeze.cfg". Error: Boot loader didn't return any data! It seems related to the following error in dmesg [1440.163935] pygrub[3654] trap invalid

Forwarding to you original patch requested. It works for me. Boris --- On Sun, 7/11/10, eXeC001er <execooler@gmail.com> wrote: From: eXeC001er <execooler@gmail.com> Subject: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable) To: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, July 11, 2010, 9:18 AM 1. Bug fix for error: "Error: Device

Hello , everyone I am a newcomer to xen , which i study in recent months . I have deploy the xen-4.1.2 on dell server , centos as dom0 , now , i use the vhd format to be the virtual hard disk , after i execute " xm new ***.cfg" , this vm generate the vm in "xm list" , but when i execute " xm start *** ", "Error: Boot loader didn''t return any data

Hi, I''ve run into the following error when trying to create a domU: root@jupiter:/etc/xen# xm create node0-mgmt -c Using config file "node0-mgmt". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. root@jupiter:/etc/xen# Excerpt from xend.log: [2006-09-25 14:55:48 xend 2015] DEBUG (DevController:110) DevController: writing

Can I run 8/07 fully virtualised on an Intel VT CPU (with a Linux Dom0)? I gave up on 11/06 because of real mode problems. If not, does anyone have an estimate of when this might be possible, if at all? Thanks - Evan

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

Hello, I would like to use the kernel in the domU, so that a user can install it's own kernel. While starting the domU with pygrub I get the following error: "Error: Boot loader didn't return any data!" This is the configfile of the domU: -------------- # # Configuration file for the Xen instance lenny.vandervlis.nl, created # by xen-tools 3.9 on Sun Oct 19 15:46:03 2008. # #

>Maybe it is obsolete??? Who knows...However, I found ubuntu-server-xen and installed >that instead. However, I installed, as far as I can say, all xen packages and now I''m >looking for some sort of a HowTo. Haven''t found one yet for Ubuntu Server 9.04 aka >Jaunty. Shouldn''t I need a XEN-Kernel? http://bderzhavets.blogspot.com/2009/05/deployment-xen-3.html

Hi, I''m using a custom block script in my xen setup and when started, it creates a new device node pointing to some network resources. Now I noticed that the script is called twice for the root block, the first time for pygrub most likely, but is only stopped once ... I don''t mind creating two devices node, but then I need to destroy both ... Is this a known issue ? Cheers,

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Following a Xen tutorial but can''t get the VM (PV Squeeze) running. After doing: # xm create -c /etc/xen/tutorial-pv-guest.cfg The prompt just sits there. Opening another terminal: # xm list /usr/lib/python2.7/dist-packages Name ID Mem VCPUs State Time(s) Domain-0 0 7199 4 r----- 40.6

Hello. I recently tried installing NetBSD-5 on xen-4.0.1-rc5, which resulted in no network (xennet0 can''t get IPs per dhclient and has no connectivity if set by hand). Tried it with netBSD-5.1-RC3-1 i386 PAE & amd64, netBSD-5.0 and even 4, all with the same result. On a older xen version (3.3.1) networking works fine, so I assume it''s a xen bug, and not a netBSD-kernel

I have NexentaCP2 (Opensolaris b104+). Parameters for the kernel: ''zfs-bootfs=syspool/rootfs-nmu-000,bootpath=/xpvd/xdf@0:a'' Pygrub returns: ''zfs-bootfs=syspool/30,bootpath=/xpvd/xdf@0:a'' Result: Boot with pygrub don''t work. What is "30" in syspool/30 ? _______________________________________________ Xen-users mailing list

After upgrade via http://download.opensuse.org/repositories/Virtualization:/openSUSE11.3/openSUSE_11.3/src/xen-4.0.1_21326_01-1.1.src.rpm with any "kotd" or 2.6.34.4-2.2-xen VFB gets broken . It worked with original  Xen 4.0, no matter of  some additional patching to support ZFS 24 has been done and 4.0 src.rpm has been rebuilt to reinstall 4.0   In particular,  virt-install fails to

Dear *, I''m more used to work with RedHat like OSes. Still, I did not denied the request from a user who wants a domU based on ubunto. I usually use virt-install to do the job, with a script similar to this one: #!/bin/sh BASE=SL-4.7-i386-pv \ virt-install --nographics \ --nonsparse \ --paravirt \ --noreboot \