Displaying 20 results from an estimated 4000 matches similar to: "Bug#649349: xen-hypervisor-4.1-amd64: pygrub fails due to invalid opcode trapped"
2008 Nov 26
1
Pygrub problem
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.
#
#
2012 Oct 19
6
"Boot loader did not return any data" to make HVM to PV
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
2011 Oct 02
0
Bug#644100: pygrub error if the root disk value is not the first in the list.
Package: xen-utils-4.0
Version: 4.0.1-2
Severity: normal
File: pygrub
pygrub error when trying to run a image created by xen-create-image
with partitions option.
----------------------------------------------------------------------------------------------------------------------------------------
[2011-10-02 21:36:08 1512] DEBUG (XendDomainInfo:101)
XendDomainInfo.create(['vm',
2012 Mar 07
2
PV DomU stopped responding, won't boot, stuck in paused state
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
2008 Jun 25
0
domUs doesn''t boot after upgrade to xen 3.2
Hi all, after upgrading from xen 3.0 to xen 3.2 I cannot start my
domUs: I get: VmError: Boot loader didn''t return any data!
Suggestions?
This is the log
[2008-06-25 11:24:53 2755] DEBUG (XendDomainInfo:84)
XendDomainInfo.create([''vm'', [''name'', ''engtest3.infolan''], [''memory'',
''2048''],
2011 Nov 15
7
How to get pygrub to load grub2 guest on Squeeze Dom0.
Hi,
I''m trying to install a FC 16 PV guest. After installation the guest
doesn''t load with: Error: Boot loader didn''t return any data!
xend.log:
[2011-11-14 18:57:32 32321] ERROR (XendBootloader:214) Boot loader didn''t
return any data!
[2011-11-14 18:57:32 32321] ERROR (XendDomainInfo:483) VM start failed
Traceback (most recent call last):
File
2012 Jul 20
0
RuntimeError: Unable to find partition containing kernel
Hardware:
2x Intel Xeon Quad-Core 2.33GHz
24GB FBDIMM RAM
2x 2TB HDD in RAID-1
Intel Server Board S5400SF
Setup:
Arch Linux x86_64
Xen 4.1.2
Grub2 Multiboot
Synopsis:
I set up a new VM for Debian Squeeze following instructions here:
http://www.howtoforge.com/installing-debian-squeeze-6.0-domu-on-centos-5.5-x86_64-dom0.
Partitioning & installation completed correctly. When I tried to run the
2011 Oct 29
0
Bug#644100: Boot loader didn't return any data! if reboot domU with disk DRBD
Package: xen-utils-4.0
Version: 4.0.1-2
If you reboot with the DomU disk DRBD domain destroy.
pygrub error when trying to run a image on DRBD device
My config DomU
------------------------------------------------------
bootloader = '/usr/lib/xen-default/bin/pygrub'
vcpus = '1'
memory = '256'
cpus="8-15"
root = '/dev/xvda2 ro'
#disk
2010 Aug 01
6
Opensolaris domU - install ok, pygrub boot not ok.
Hi All,
Debian squeeze, Xen 4.0, 2.6.32-5
I successfully installed opensolaris, but when trying to convert to
pygrub it just hangs.
root@vhost2:/var/log/xen# xm create /etc/xen/opensolaris.cfg -c
Using config file "/etc/xen/opensolaris.cfg".
root@vhost2:/etc/xen# xm list
Name ID Mem VCPUs State Time(s)
Domain-0
2011 Aug 04
3
[Q] VmError: Disk isn''t accessible with tap2:tapdisk:vhd
I''m newbie Xen-4.1.1
I''m trying to boot DomU with the following configuration.
Sometime DomU boot, but sometime boot failed
I''m not sure what is the problem.
I can attach that image with tap-ctl on Dom0.
Does anybody advice me about this problem??
Sincerely
* Environment
OS : Scientific Linux 6.1 x86_64
Kernel : 2.6.32.43
2012 Jun 28
10
Error: Boot loader didn't return any data [pygrub boot debian wheezy alpha1 netinst ISO]
Note: I could simply direct boot the appropriate kernel/initrd to get
the alpha1 installation going as always done in the past, but I think
this should work. The Debian alpha 1 installer page says it should.
Details
$ sudo xm create -c wheezytest.cfg
Using config file "./wheezytest.cfg".
Error: Boot loader didn''t return any data!
direct pygrub test run:
# pygrub
2008 Jul 03
3
xm create fails with ''elf_xen_note_check: ERROR:''
Hi --
I''m getting this error even though I have correct DVD ISO image for snv_92.
bash-3.2# uname -a
SunOS stoakly2 5.11 snv_92 i86pc i386 i86xpv
bash-3.2# xm create snv.py
Using config file "./snv.py".
Error: (2, ''Invalid kernel'', ''elf_xen_note_check: ERROR: Will only load
images built for the generic loader or Linux images'')
bash-3.2#
2011 Dec 01
3
How to solve "Error: Boot loader didn't return any data"
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
2007 Jan 05
10
[PATCH 1/7] Fix pygrub path on Solaris
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
2012 Nov 02
9
Custom block script started twice for root block but only stopped once
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,
2010 Sep 27
8
pygrub question
Hi,
I''ve prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host running
Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is
running a 2.6.32-24-server kernel from the Ubuntu repositories, which is
(must be :-) ) xen-aware. The domU uses pygrub to boot and it works like
a charm.
Now I''m trying to deploy this domU on a Xen 3.2-1 host running Debian
Etch on kernel
2009 Mar 12
0
Successfully running VM, subsequently startup gives this error -- VmError: Boot loader didn''t return any data!
Hi
I have configured few VMs with RHEL5,32 bit, but some VMs
after successful stop/restart few times, suddenly they start giving
following error from "xm create vm1.cfg" startup.
----
Error: (''c618d493-a696-7637-333d-bd891fa41ac2'', ''VM_metrics'')
----
If i replace system.img, they starts working again. This is what i see in xend.log file.
This happens
2008 Nov 27
6
Bug#507020: xen-utils-3.2-1: Pygrub says "Error: Boot loader didn't return any data!"
Package: xen-utils-3.2-1
Version: 3.2.1-2
Severity: normal
When my domU uses this configuration:
---
root = '/dev/sda2 ro'
disk = [
'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w',
'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w',
]
---
Pygrub gives the error "Error: Boot loader didn't return
2013 Feb 26
1
Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
Package: xen
Version: 4.0.1-5.5
Severity: critical
--- Please enter the report below this line. ---
Hi!
Since the update last weekind in stable/squeeze I'm experiencing
problems with running Xen on amd64 and multiple domUs losing their
network connection/VIFs.
From
http://blog.windfluechter.net/content/blog/2013/02/26/1597-xen-problems-vms-2632-5-xen-amd64
Unfortunately this update
2012 Sep 12
2
new pv stuck in pause
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