5:11 a.m.
Thanks Mr.Stefan
I was getting some errors when i ran like xm create
libvirt-ttylinux.conf
----------------------------------------------------------------------------------------------------------------------------------------
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
------------------------------------------------------------------------
So this time as sure that there is some problem with my configuration
file. I googled , then I found some solution to change the ramdisk
option by some command mentioned in the following link.
http://www.virtuatopia.com/index.php/A_Xen_Guest_OS_fails_to_boot_with_a_....
But after doing this when I restart my process by "xm create..." and "virsh
console..." , I get
--------------------------------------------------------------
Creating root device.
Mounting root filesystem.
ext3: No journal on filesystem on sda1
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
--------------------------------------------------------------------------------------------------------------------------
Similary when I try other way by changing the ramdisk option in
ttylinux.xml file and use "virsh -c xen:/// create
libvirt-ttylinux.xml" , then virsh console domainname,
I get some kernel error
--------------------------------------------------------------------------------------------------
..............................................................
Initalizing network drop monitor service
Freeing unused kernel memory: 176k freed
Write protecting the kernel read-only data: 390k
Registering block device major 8
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel(a)redhat.com
device-mapper: dm-raid45: initialized v0.2594l
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
ext3: No journal on filesystem on sda1
Kernel panic - not syncing: Attempted to kill init!
--------------------------------------------------------------------------------------------------
So , There is something terribly wrong with my kernel options in the
configuration file in both cases, that doesn't allow the image to boot.
Can you identify the nature of the error?
Can You help me out in someway?
Thanks
________________________________
Sankamesh <sankamesh_rb(a)yahoo.co.in> wrote on
04/12/2010 04:29:36 AM:
Thanks Mr. Stefan
Will that crash mainly be due to the kernel ?
Since am not sure
about that,else I should try with different image.
When I use via a config file using "xm create
libvirt-ttylinux.conf
", then the domain runs stable....
But when I use the virsh -c xen:/// define libvirt-ttylinux.xml"
and
"virsh start ttyimage, it crashes after sometime.
The ibvirt-ttylinux.conf file ::
--------------------------------------------------------------------------------------------------------------------------------
kernel = "/boot/vmlinuz-2.6.18-164.2.1.el5xen"
ramdisk= "/boot/initrd-2.6.18-164.2.1.el5xen.img"
memory = 64
Maybe try to give it some more memory...
Otherwise I can just guess as to why there is such
a difference in this vm running stable. Are there any significant difference
between an 'xm list' after the 'xm create' and an
'xm list' after the 'virsh -c ... define'? Did you ever try 'xm new
<vm
config file name>' followed
by an 'xm start <domainname>'?
name = "ttylinux"
disk = ['file:/usr/local/ttylinux-xen-libvirt/ttylinux-xen.img,sda1,w']
root = "/dev/sda1 ro"
vif = ['']
--------------------------------------------------------------------------------------------------------------------------------
I give the same Xen kernel parameter here in
xml file, and use virsh
to create domain
---------------------------------------------------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="utf-8"?>
<domain type='xen'>
<name>ttyimage</name>
<os>
<type>linux</type>
<kernel>/boot/vmlinuz-2.6.18-164.2.1.el5xen</kernel>
<initrd>/boot/initrd-2.6.18-164.2.1.el5xen.img</initrd>
</os>
<memory>65536</memory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<graphics type='vnc' port='5900'/>
<disk type='file'>
<source file='/usr/local/ttylinux-xen-libvirt/ttylinux-xen.img'
/>
<target dev='sda1' />
</disk>
<interface type='bridge'>
<source bridge='virbr0'
/>
<mac address='00:1d:60:ec:ae:1c'
/>
<target dev='testnimb-0'
/>
</interface>
</devices>
</domain>
---------------------------------------------------------------------------------------------------------------------------------------
My Boot grub file data::
--------------------------------------------------------------------------------------------------------------------------------------
title Scientific Linux (2.6.18-164.2.1.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-164.2.1.el5
module /vmlinuz-2.6.18-164.2.1.el5xen ro root=LABEL=/1
rhgb quiet
module /initrd-2.6.18-164.2.1.el5xen.img
--------------------------------------------------------------------------------------------------------------------------------------
Why is this difference between the xm (when i destroy the
image,domain is also destroyed) and virsh (domain is not destroyed
while destroying the image) .
xm new <vm definition filename> -> xm start
<domainname> -> xm destroy <domainname> -> xm delete
<domainname>
is similar to
virsh ... define -> virsh start <domainname>
-> virsh destroy <domainname> -> virsh undefine <domainname>
Stefan
I doubt that am making some mistake with the xml file .... Is that
true?
Kindly give some suggestions
Thanks
libvir-list-bounces(a)redhat.com wrote on 04/10/2010
09:47:17
AM:
> libvir-list
>
> Hello,
>
> Thanks Alex
>
> I created a domain using "virsh -c xen:/// define
libvirt-ttylinux.xml" and
> "virsh start ttyimage" for a simple ttyimage.
>
> Problem I face is that the image shutsdown immedialtely once
virsh
> start guest is typed.
> I checked the Xend Logs
>
----------------------------------------------------------------------------------------------------------
> ---[2010-04-11 07:08:02 xend 3155] DEBUG (DevController:116)
> DevController: writing {'frontend-id': '6', 'domain':
'ttyimage',
[...]
> [2010-04-11 07:08:02 xend 3155] DEBUG (vfbif:11) Spawn: ['/usr/lib/
> xen/bin/qemu-dm', '-M', 'xenpv', '-d', '6',
'-domain-name',
> 'ttyimage', '-vnc', '127.0.0.1:0', '-vncunused',
'-k', 'en-us']
> [2010-04-11 07:08:02 xend.XendDomainInfo 3155] DEBUG
> (XendDomainInfo:992) Storing VM details: {'shadow_memory': '0',
> 'uuid': 'd5e916b0-bc2d-01f9-8156-4808c754f67a', 'on_reboot':
> 'restart', 'start_time': '1270937282.29',
'on_poweroff': 'destroy',
> 'name': 'ttyimage', 'xend/restart_count': '0',
'vcpus': '1',
> 'vcpu_avail': '1', 'memory': '64',
'on_crash': 'destroy', 'image':
> '(linux (kernel /boot/vmlinuz-2.6.18-164.2.1.el5xen))', 'maxmem':
'64'}
> [2010-04-11 07:08:02 xend.XendDomainInfo 3155] DEBUG
> (XendDomainInfo:1027) Storing domain details: {'console/ring-ref':
> '65674', 'console/port': '2', 'name':
'ttyimage', 'console/limit':
> '1048576', 'vm': '/vm/d5e916b0-bc2d-01f9-8156-4808c754f67a',
> 'domid': '6', 'cpu/0/availability': 'online',
'memory/target':
> '65536', 'store/ring-ref': '65675', 'store/port':
'1'}
> [2010-04-11 07:08:02 xend.XendDomainInfo 3155] DEBUG
> (XendDomainInfo:1249) XendDomainInfo.handleShutdownWatch
> [2010-04-11 07:08:02 xend 3155] DEBUG (DevController:158) Waiting
> for devices vif.
> [2010-04-11 07:08:02 xend 3155] DEBUG (DevController:164) Waiting
for 0.
> [2010-04-11 07:08:02 xend 3155] DEBUG (DevController:509)
> hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status.
> [2010-04-11 07:08:51 xend 3155] INFO (XendDomain:387) Domain
> ttyimage (6) unpaused.
> [2010-04-11 07:08:54 xend.XendDomainInfo 3155] WARNING
> (XendDomainInfo:1177) Domain has crashed: name=ttyimage id=6.
You domain crashed here... Is the VM image and kernel in that
image
known to work?
Regards,
Stefan
Send free SMS to your Friends on Mobile from your Yahoo! Messenger.
Download Now! http://messenger.yahoo.com/download.php
Send free SMS to your Friends on Mobile from your Yahoo! Messenger. Download Now!
http://messenger.yahoo.com/download.php