Re: [Xen-users] guest creation problem on pv dom0 kernel

["Fajar A. Nugraha" <list@xxxxxxxxx>]

On Thu, Mar 10, 2011 at 3:07 PM, Tapas Mishra <mightydreams@xxxxxxxxx> wrote:
> and now when I add bridge=virbr0
>
> then I have following logs
>
> domain-builder-ng.log
> http://pastebin.com/8W45hjCV
>
>
>  xend-debug.log
> http://pastebin.com/634FaJQP
>
>  xend.log
> http://pastebin.com/y7wWs19K
>
> qemu-dm-ubuntu.vm.log
> http://pastebin.com/cRNqUGRf
>
>  xen-hotplug.log
> is empty as it was empty when the line
> bridge=virbr0 was not there.
>

Why do you use xvda1?

I gave you an example PV domU config, which has "xvda" on it (NOT
xvda1). There's also xm-debian.cfg on
http://archive.ubuntu.com/ubuntu/dists/maverick/main/installer-i386/current/images/netboot/xen/
(which also uses xvda, not xvda1). Yet you choose (from the log you
provided)

['device', ['vbd', ['uname', 'file:/mnt/1/vm1.img'], ['dev', 'xvda1'],
['mode', 'w']]],
['device', ['vbd', ['uname', 'file:/mnt/1/vm1-swap.img'], ['dev',
'xvda2'], ['mode', 'w']]]

I've said this many times, it's fine if you want to introduce your own
changes, but only if you know what they're for. Don't go complaining
to others if your change breaks things. There's a difference between
mapping as xvda and xvda1, and if you want to use normal OS installer
you need to map it as a disk (xvda) and not a partition (xvda2).

To be honest though, while that change will prevent the installer from
working, the domU should still start. I don't know where you went
wrong. Probably cause you use a path with single quote (') in it
("/home/bond/Documents/ISO's/forvm/vmlinuz").

Your xend.log also seems weird. It should show something like

[2011-03-10 14:58:12 7832] DEBUG (XendDomainInfo:1891)
XendDomainInfo.handleShutdownWatch
[2011-03-10 14:58:12 7832] DEBUG (DevController:139) Waiting for devices vif2.
[2011-03-10 14:58:12 7832] DEBUG (DevController:139) Waiting for devices vif.
[2011-03-10 14:58:12 7832] DEBUG (DevController:144) Waiting for 0.
[2011-03-10 14:58:12 7832] DEBUG (DevController:628)
hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status.
[2011-03-10 14:58:12 7832] DEBUG (DevController:628)
hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status.
[2011-03-10 14:58:12 7832] DEBUG (DevController:642) hotplugStatusCallback 1.
[2011-03-10 14:58:12 7832] DEBUG (DevController:139) Waiting for devices vscsi.
[2011-03-10 14:58:12 7832] DEBUG (DevController:139) Waiting for devices vbd.
[2011-03-10 14:58:12 7832] DEBUG (DevController:144) Waiting for 51712.
[2011-03-10 14:58:12 7832] DEBUG (DevController:628)
hotplugStatusCallback
/local/domain/0/backend/vbd/6/51712/hotplug-status.
[2011-03-10 14:58:13 7832] DEBUG (DevController:628)
hotplugStatusCallback
/local/domain/0/backend/vbd/6/51712/hotplug-status.
[2011-03-10 14:58:13 7832] DEBUG (DevController:642) hotplugStatusCallback 1.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for
devices ioports.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices irq.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices vkbd.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices vfb.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for
devices console.
[2011-03-10 14:58:13 7832] DEBUG (DevController:144) Waiting for 0.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices pci.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices tap2.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices tap.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices vusb.
[2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices vtpm.
[2011-03-10 14:58:13 7832] INFO (XendDomain:1206) Domain ubuntu (6) unpaused.


While yours simply show

[2011-03-10 13:30:04 1705] DEBUG (DevController:628)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-03-10 13:31:44 1705] DEBUG (XendDomainInfo:3053)
XendDomainInfo.destroy: domid=1

Perhaps udevd is dead?
Were you able to create any other domUs (whether using virt manager or
manually)?

At this point I'd suggest:
- reboot the dom0
- use "normal" path (without single or double quote it it's name) for
kernel and initrd
- make sure udevd is not dead
- make sure you the disk image and bridge that you're going to use exist
- map domUs device as disk (xvda)
- try creating the domU

If that doesn't work, I don't know what went wrong in your setup.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users