----- "Aaron Clark" ophidian@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 [serial] console? Does the dom0 ever unpause the guest? (It should say in the logs.)
On Sat, Mar 27, 2010 at 11:53:41PM -0500, Christopher G. Stach II wrote:
----- "Aaron Clark" ophidian@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 [serial] console? Does the dom0 ever unpause the guest? (It should say in the logs.)
Yeah, and remove the vfb (graphical vnc console) from the guest, so you can then do:
xm create -f /etc/xen/guest -c
to immediately attach to the console and see the guest kernel boot messages.
-- Pasi
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 Clark"ophidian@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 [serial] console? Does the dom0 ever unpause the guest? (It should say in the logs.)
Yeah, and remove the vfb (graphical vnc console) from the guest, so you can then do:
xm create -f /etc/xen/guest -c
to immediately attach to the console and see the guest kernel boot messages.
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 domU to use the old kernel then try to start the domU (doesn't work) - remove the vnc lines from the guest's config via virsh edit and attempt to start (doesn't work)
I do not have any serial console stuff set up, so I'll need a little bit more detailed instructions to get that working (which files I need to modify on guest and host, what to put where, etc).
I have attached the snippet of the xend.log from my latest startup attempt and the virsh xml in use while it is 'running' but not actually working.
Aaron
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 Clark"ophidian@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 [serial] console? Does the dom0 ever unpause the guest? (It should say in the logs.)
Yeah, and remove the vfb (graphical vnc console) from the guest, so you can then do:
xm create -f /etc/xen/guest -c
to immediately attach to the console and see the guest kernel boot messages.
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 domU to
use the old kernel then try to start the domU (doesn't work)
- remove the vnc lines from the guest's config via virsh edit and
attempt to start (doesn't work)
I do not have any serial console stuff set up, so I'll need a little bit more detailed instructions to get that working (which files I need to modify on guest and host, what to put where, etc).
You don't need a serial console to see the _guest_ kernel boot messages. You just disable vfb (graphical console) from the guest, and then the guest kernel messages will automatically go to the Xen text console:
You can see the full guest kernel boot messages like this:
xm create -f /etc/xen/<guest> -c
Edit the /etc/xen/<guest> cfgfile first, and remove the vfb line to disable graphical console.
I have attached the snippet of the xend.log from my latest startup attempt and the virsh xml in use while it is 'running' but not actually working.
In your xml config there still was graphical console configured.
-- Pasi
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 domU to
use the old kernel then try to start the domU (doesn't work)
- remove the vnc lines from the guest's config via virsh edit and
attempt to start (doesn't work)
I do not have any serial console stuff set up, so I'll need a little bit more detailed instructions to get that working (which files I need to modify on guest and host, what to put where, etc).
You don't need a serial console to see the _guest_ kernel boot messages. You just disable vfb (graphical console) from the guest, and then the guest kernel messages will automatically go to the Xen text console:
You can see the full guest kernel boot messages like this:
xm create -f /etc/xen/<guest> -c
Edit the /etc/xen/<guest> cfgfile first, and remove the vfb line to disable graphical console.
I removed the vfb line from the /etc/xen/<guest> file... still doesn't start and the console does not attach.
[root@Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c Using config file "/etc/xen/Belldandy". Started domain Belldandy xenconsole: Could not read tty from store: No such file or directory
Aaron
----- "Aaron Clark" ophidian@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.
[root@Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c Using config file "/etc/xen/Belldandy". Started domain Belldandy xenconsole: Could not read tty from store: No such file or directory
Is there anything interesting in that run's qemu log?
On 03/28/2010 11:14 PM, Christopher G. Stach II wrote:
----- "Aaron Clark"ophidian@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.
[root@Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c Using config file "/etc/xen/Belldandy". Started domain Belldandy xenconsole: Could not read tty from store: No such file or directory
Is there anything interesting in that run's qemu log?
The contents of the qemu log are: domid: 5 qemu: the number of cpus is 1 Watching /local/domain/5/logdirty/next-active Watching /local/domain/0/device-model/5/command qemu: could not open serial device 'none'
Note that the qemu-dm process is listed as 'defunct' in ps.
One interesting line from the xend.log that I don't know how to interpret is: [2010-03-29 21:03:53 xend.XendDomainInfo 3186] DEBUG (XendDomainInfo:633) Checking for duplicate for uname: /dev/SystemsVG/Belldandy [phy:/dev/SystemsVG/Belldandy], dev: hda:disk, mode: w [2010-03-29 21:03:53 xend 3186] DEBUG (blkif:27) exception looking up device number for hda:disk: [Errno 2] No such file or directory: '/dev/hda:disk'
Not sure if it means anything but thoughts appreciated. This is **not** the last line in the log.
Aaron
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 work)
- while in the old kernel-xen, switch the grub config for the domU to
use the old kernel then try to start the domU (doesn't work)
- remove the vnc lines from the guest's config via virsh edit and
attempt to start (doesn't work)
I do not have any serial console stuff set up, so I'll need a little bit more detailed instructions to get that working (which files I need to modify on guest and host, what to put where, etc).
You don't need a serial console to see the _guest_ kernel boot messages. You just disable vfb (graphical console) from the guest, and then the guest kernel messages will automatically go to the Xen text console:
You can see the full guest kernel boot messages like this:
xm create -f /etc/xen/<guest> -c
Edit the /etc/xen/<guest> cfgfile first, and remove the vfb line to disable graphical console.
I removed the vfb line from the /etc/xen/<guest> file... still doesn't start and the console does not attach.
[root@Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c Using config file "/etc/xen/Belldandy". Started domain Belldandy xenconsole: Could not read tty from store: No such file or directory
Hmm.. only now I notice you're trying to start a HVM guest. HVM guests will pretty much require graphical console..
Sorry for the wrong tips. The stuff I wrote was for PV guests.
-- Pasi
- 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.
- Check paths to hvmloader, qemu-dm
- post more log files, if you have.
2010/3/29 Pasi Kärkkäinen pasik@iki.fi
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 work)
- while in the old kernel-xen, switch the grub config for the domU to
use the old kernel then try to start the domU (doesn't work)
- remove the vnc lines from the guest's config via virsh edit and
attempt to start (doesn't work)
I do not have any serial console stuff set up, so I'll need a little
bit
more detailed instructions to get that working (which files I need to modify on guest and host, what to put where, etc).
You don't need a serial console to see the _guest_ kernel boot
messages.
You just disable vfb (graphical console) from the guest, and then the guest kernel messages will automatically go to the Xen text console:
You can see the full guest kernel boot messages like this:
xm create -f /etc/xen/<guest> -c
Edit the /etc/xen/<guest> cfgfile first, and remove the vfb line to
disable graphical console.
I removed the vfb line from the /etc/xen/<guest> file... still doesn't start and the console does not attach.
[root@Yggdrasil ~]# xm create -f /etc/xen/Belldandy -c Using config file "/etc/xen/Belldandy". Started domain Belldandy xenconsole: Could not read tty from store: No such file or directory
Hmm.. only now I notice you're trying to start a HVM guest. HVM guests will pretty much require graphical console..
Sorry for the wrong tips. The stuff I wrote was for PV guests.
-- Pasi
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
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 to hvmloader, qemu-dm
They do exist. Keep in mind that I have another domU with pretty much the same configuration that is functioning fine on this machine.
- post more log files, if you have.
What other log files would help?
Here is the contents of the xen config generated by virsh: name = "Belldandy" uuid = "2627c318-d3a7-83a6-522c-fa2586fb86be" maxmem = 256 memory = 256 vcpus = 1 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 1 apic = 1 localtime = 0 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib64/xen/bin/qemu-dm" disk = [ "phy:/dev/SystemsVG/Belldandy,hda,w" ] vif = [ "mac=00:16:3e:1d:43:df,bridge=xenbr0,script=vif-bridge" ] parallel = "none" serial = "none"
Aaron
-
Aaron Clark -
Christopher G. Stach II -
Pasi Kärkkäinen -
Sergio Charpinel Jr.