Aaron,
Seems to be something related to your block device.
Try this config file:
name = Belldandy
maxmem = 256
memory = 256
vcpus = 1
builder = hvm
kernel = /usr/lib/xen/boot/hvmloader
boot = c
on_poweroff = destroy
on_reboot = restart
on_crash = restart
device_model = /usr/lib64/xen/bin/qemu-dm
On 03/28/2010 11:14 PM, Christopher G. Stach II wrote:
- Aaron Clarkophid...@ophidian.homeip.net wrote:
I removed the vfb line from the /etc/xen/guest file... still doesn't
start and the console does not attach.
[r...@yggdrasil ~]# xm create -f /etc/xen/Belldandy -c
Using config file
On 03/29/2010 08:18 AM, Sergio Charpinel Jr. wrote:
- Try to unset any graphical option and run the domU, maybe its missing some
lib, like sdl. I don't know how to do it in virsh, because in xen cfg,
default vnc option is 1.
Already tried, doesn't make a lick of difference.
- Check paths
- Aaron Clark ophid...@ophidian.homeip.net wrote:
qemu: could not open serial device 'none'
http://os-drive.com/files/docbook/xen-faq.html#serial_console_hvm
Does the LV show that it's open (or ever changes state) when the VM attempts to
boot? Did you try taking a snapshot of the LV and
On 03/29/2010 09:37 PM, Christopher G. Stach II wrote:
- Aaron Clarkophid...@ophidian.homeip.net wrote:
qemu: could not open serial device 'none'
http://os-drive.com/files/docbook/xen-faq.html#serial_console_hvm
I will give this a look to see if it shed any light on the situation.
On Sat, Mar 27, 2010 at 11:53:41PM -0500, Christopher G. Stach II wrote:
- Aaron Clark ophid...@ophidian.homeip.net wrote:
What steps should I take next to debug this?
Downgrade back to where you were bit by bit (or just guess that it's dom0's
kernel) and see when it starts working
On 03/28/2010 07:59 AM, Pasi Kärkkäinen wrote:
On Sat, Mar 27, 2010 at 11:53:41PM -0500, Christopher G. Stach II wrote:
- Aaron Clarkophid...@ophidian.homeip.net wrote:
What steps should I take next to debug this?
Downgrade back to where you were bit by bit (or just guess that it's
On Sun, Mar 28, 2010 at 12:45:58PM -0400, Aaron Clark wrote:
On 03/28/2010 07:59 AM, Pasi Kärkkäinen wrote:
On Sat, Mar 27, 2010 at 11:53:41PM -0500, Christopher G. Stach II wrote:
- Aaron Clarkophid...@ophidian.homeip.net wrote:
What steps should I take next to debug this?
Downgrade
On 03/28/2010 03:36 PM, Pasi Kärkkäinen wrote:
On Sun, Mar 28, 2010 at 12:45:58PM -0400, Aaron Clark wrote:
Ok, I've tried the following now:
- rebooted the dom0 into the previous, working kernel-xen and start domU
(doesn't work)
- while in the old kernel-xen, switch the grub config for the
- Aaron Clark ophid...@ophidian.homeip.net wrote:
I removed the vfb line from the /etc/xen/guest file... still doesn't
start and the console does not attach.
[r...@yggdrasil ~]# xm create -f /etc/xen/Belldandy -c
Using config file /etc/xen/Belldandy.
Started domain Belldandy
On Sun, Mar 28, 2010 at 06:39:01PM -0400, Aaron Clark wrote:
On 03/28/2010 03:36 PM, Pasi Kärkkäinen wrote:
On Sun, Mar 28, 2010 at 12:45:58PM -0400, Aaron Clark wrote:
Ok, I've tried the following now:
- rebooted the dom0 into the previous, working kernel-xen and start domU
(doesn't
I have a dom0 machine running CentOS 5.4 with all the latest updates
using Xen as my hypervisor. I am using Xen in part because this machine
was set up prior to KVM being included in RHEL, and in part because
KVM's network bridging configuration is not nearly as simple as Xen's.
The dom0
- Aaron Clark ophid...@ophidian.homeip.net wrote:
What steps should I take next to debug this?
Downgrade back to where you were bit by bit (or just guess that it's dom0's
kernel) and see when it starts working again.
What does the busted guest say when it tries to boot while you watch its
13 matches
Mail list logo
