Re: [Possible SPAM] Re: [Xen-users] Can't boot in any domU

[Stephan Seitz <s.seitz@xxxxxxxxxxxx>]

to give a quick and dirty solution:

chmod 000 /etc/init.d/hwclock*

in the domU image.

this is a known issue with ubuntu's way of ignoring
independend_wallclock.


Pascal Nobus schrieb:
> This helps a little.
> 
>  * Setting preliminary keymap...
>         [ 4525.162990] Serial: 8250/16550 driver $Revision: 1.90 $ 4
> ports, IRQ sharing enabled
> Couldnt get a file descriptor referring to the console
> Couldnt get a file descriptor referring to the console
> Couldnt get a file descriptor referring to the console
> Couldnt get a file descriptor referring to the console
> Couldnt get a file descriptor referring to the console
> Couldnt get a file descriptor referring to the console
>                   [ OK ]
>  * Setting the system clock
> 
> 
> And then it freezes again :-(
> 
> 
> Mark Williamson schreef:
>>> After having problems with SMP, disabled Hyperthreading and did a fresh
>>> install of Ubuntu7.10 / xen-3.10
>>>
>>> The only problem I have is that I can't boot any domU!
>>>
>>> On the screen I see:
>>> [ 2473.641941] md: raid5 personality registered for level 5
>>> [ 2473.642062] md: raid4 personality registered for level 4
>>> [ 2473.666833] md: raid10 personality registered for level 10
>>> [ 2473.908267] kjournald starting.  Commit interval 5 seconds
>>> [ 2473.908561] EXT3-fs: mounted filesystem with ordered data mode.
>>> .... and then it freezes
>> Sounds like it's running OK but not sending output to the console.
>>
>>> xm list gives:
>>> Name                              ID   Mem VCPUs      State   Time(s)
>>> Domain-0                           0   938     1     r-----     20.5
>>> xen1.example.com                   1    64     1     ------    191.4
>> That's fine; on an uniprocessor machine you'll never see a guest in the 
>> running state because in order for you to run "xm list" dom0 must be running.
>>
>> If you try adding
>>
>> extra = "xencons=tty console=tty"
>>
>> to the domain config file, does that help?
>>
>> Cheers,
>> Mark
>>
>>> in xend.log I see:
>>> [2007-12-04 15:29:48 4488] DEBUG (__init__:1094) Storing domain details:
>>> {'console/ring-ref': '14835', 'image/entry': '32222
>>> 74048', 'console/port': '2', 'store/ring-ref': '14836', 'image/loader':
>>> 'generic', 'vm': '/vm/7eff4749-5541-aa5d-9522-8127ca
>>> fb09a4', 'control/platform-feature-multiprocessor-suspend': '1',
>>> 'image/hv-start-low': '4118806528', 'image/guest-os': 'linu
>>> x', 'image/features/writable-descriptor-tables': '1', 'image/virt-base':
>>> '3221225472', 'memory/target': '65536', 'image/gues
>>> t-version': '2.6', 'image/features/supervisor-mode-kernel': '1',
>>> 'image/pae-mode': 'yes', 'console/limit': '1048576', 'image
>>> /paddr-offset': '3221225472', 'image/hypercall-page': '3222278144',
>>> 'image/suspend-cancel': '1', 'cpu/0/availability': 'onli
>>> ne', 'image/features/pae-pgdir-above-4gb': '1',
>>> 'image/features/writable-page-tables': '1',
>>> 'image/features/auto-translated- physmap': '1', 'name': 'xen1.example.com',
>>> 'domid': '1',
>>> 'image/xen-version': 'xen-3.0', 'store/port': '1'}
>>> [2007-12-04 15:29:48 4488] DEBUG (__init__:1094)
>>> XendDomainInfo.handleShutdownWatch
>>> [2007-12-04 15:29:48 4488] DEBUG (__init__:1094) Waiting for devices vif.
>>> [2007-12-04 15:29:48 4488] DEBUG (__init__:1094) Waiting for 0.
>>> [2007-12-04 15:29:48 4488] DEBUG (__init__:1094) hotplugStatusCallback
>>> /local/domain/0/backend/vif/1/0/hotplug-status.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) hotplugStatusCallback
>>> /local/domain/0/backend/vif/1/0/hotplug-status.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) hotplugStatusCallback 1.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices usb.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices vbd.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for 769.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) hotplugStatusCallback
>>> /local/domain/0/backend/vbd/1/769/hotplug-status.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) hotplugStatusCallback 1.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for 770.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) hotplugStatusCallback
>>> /local/domain/0/backend/vbd/1/770/hotplug-status.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) hotplugStatusCallback 1.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices irq.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices vkbd.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices vfb.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices
>>> console.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for 0.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices pci.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices
>>> ioports.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices tap.
>>> [2007-12-04 15:29:49 4488] DEBUG (__init__:1094) Waiting for devices vtpm.
>>> [2007-12-04 15:29:49 4488] INFO (__init__:1094) Domain xen1.example.com
>>> (1) unpaused.
>>>
>>>
>>>
>>> #xen1.example.com.cfg
>>> kernel      = '/boot/vmlinuz-2.6.22-14-xen'
>>> ramdisk     = '/boot/initrd.img-2.6.22-14-xen'
>>> memory      = '64'
>>> vcpus = '1'
>>> root        = '/dev/hda1 ro'
>>> disk        = [
>>> 'file:/home/xen/domains/xen1.example.com/disk.img,hda1,w',
>>> 'file:/home/xen/domains/xen1.example.com/swap.img,hda2,w' ]
>>> name        = 'xen1.example.com'
>>> vif         = [ 'ip=192.168.2.101' ]
>>>
>>>
>>> Tried  nosmp noapic acpi=off with the root= in the DomU config-file, but
>>> always the same.
>>>
>>> Any suggestions?
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>
>>
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


-- 
Stephan Seitz
Senior System Administrator

*netz-haut* e.K.
multimediale kommunikation

zweierweg 22
97074 würzburg

fon: +49 931 2876247
fax: +49 931 2876248

web: www.netz-haut.de <http://www.netz-haut.de/>

registriergericht: amtsgericht würzburg, hra 5054

Attachment: s_seitz.vcf
Description: Vcard

Attachment: signature.asc
Description: OpenPGP digital signature

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