> -----Original Message-----
> From: Octavian Teodorescu [mailto:octav@xxxxxxxxxxxxxxxx]
> Sent: 29 May 2007 14:48
> To: Petersson, Mats
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Can not start Guest, receiving errors
>
> Ok so I have done the following:
> config of ns1 guest domain:
> --------------
> kernel = "/boot/vmlinuz-2.6.18-8.1.4.el5xen"
> builder='linux'
>
> memory = 384
> name = "ns1"
>
> # List of which CPUS this domain is allowed to use, default Xen picks
> #cpus = "" # leave to Xen to pick
> #cpus = "0" # all vcpus run on CPU0
> #cpus = "0-3,5,^1" # run on cpus 0,2,3,5
> vcpus = 1
>
> #vif = [ 'mac=FE:FF:FF:FF:FF:FF , ip=139.185.48.214, 'bridge=xenbr1' ]
> vif = [ '', 'bridge=xenbr1' ]
>
> disk = [ 'phy:/dev/VGvhosts/root.ns1,hda1,w',
> 'phy:/dev/VGvhosts/swap.ns1,hda2,w' ]
>
> dhcp="dhcp"
>
> # Set root device.
> root = "/dev/hda1"
> #bootloader="/usr/bin/pygrub"
> ------------
>
> and I still have the following error message when I run xm
> create ns1 -c:
> ------------
> TCP bic registered
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> XENBUS: Device with no driver: device/vbd/769
> XENBUS: Device with no driver: device/vbd/770
> XENBUS: Device with no driver: device/vif/0
> XENBUS: Device with no driver: device/vif/1
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> VFS: Cannot open root device "hda1" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> ------------
> I have also installed the base CentOS packages on root.ns1 with yum.
>
> Any idea of what's wrong now?
> Thanks for the last answer, I quite understood some things
> much better.
You probably need to have a initrd to give the booting kernel the
drivers needed to continue the boot.
Note that the initrd of your Dom0 MAY work, but also may NOT work, as
it's more likely to only have the drivers backend needed for the Dom0,
rather the frontend drivers in the DomU.
--
Mats
>
>
> >>
> >>
> >>> -----Original Message-----
> >>> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> >>> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> >>> Octavian Teodorescu
> >>> Sent: 29 May 2007 12:15
> >>> To: xen-users@xxxxxxxxxxxxxxxxxxx
> >>> Subject: [Xen-users] Can not start Guest, receiving errors
> >>>
> >>> Hi guys,
> >>>
> >>> I have a CentOS installed on my system (P4- core2duo, sata
> >>> hard drive). At
> >>> installation I have also installed the Virtualization
> package which
> >>> installed xen, and made the boot record for xen.
> >>>
> >>> I realized that I don't have kernel-xen0 and kernel-xenU
> as I had in
> >>> Fedora (fedora was another unlucky experience with xen).
> My grub.conf:
> >>> =================
> >>> default=0
> >>> timeout=5
> >>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >>> hiddenmenu
> >>> title CentOS (2.6.18-8.1.4.el5xen)
> >>> root (hd0,0)
> >>> kernel /boot/xen.gz-2.6.18-8.1.4.el5
> >>> module /boot/vmlinuz-2.6.18-8.1.4.el5xen ro root=LABEL=/
> rhgb quiet
> >>> module /boot/initrd-2.6.18-8.1.4.el5xen.img
> >>> title CentOS (2.6.18-8.el5xen)
> >>> root (hd0,0)
> >>> kernel /boot/xen.gz-2.6.18-8.el5
> >>> module /boot/vmlinuz-2.6.18-8.el5xen ro root=LABEL=/ rhgb quiet
> >>> module /boot/initrd-2.6.18-8.el5xen.img
> >>> ===========
> >>> The dom0 boots ok, and I didn't had any problems with it.
> >>> Xend is started.
> >>>
> >>> I am tring to create a virtual machine (initially I
> wanted to install
> >>> FreeBSD, but I've read just before posting that can not be
> >>> paravirtualized, so I'll use another version of linux or
> the same).
> >>> I have the following config file called linux:
> >>
> >> Is this supposed to be a para-virtual or a HVM (fully virtualized)
> >> domain - your config file seems a bit like a mix of the two.
> >>
> >> Is this a different config than the one below?
> >>> ------------------
> >>> #kernel = "/boot/vmlinuz-2.6.10-xenU"
> >>> kernel = "/boot/vmlinuz-2.6.18-8.1.4.el5xen"
> >>>
> >>> # The domain build function. Default is 'linux'.
> >>> builder='linux-test'
> >>
> >> As far as I'm aware, the only valid choices here are: "linux",
> >> "hvmbuilder" and (I think) "solaris". You can't introduce your own
> >> "builder" option without many changes to the tools chain
> involved in
> >> domain creation.
> >>>
> >>> memory = 512
> >>>
> >>> name = "bsd"
> >>
> >> Probably not what you wanted, but works OK.
> >>>
> >>> # List of which CPUS this domain is allowed to use,
> default Xen picks
> >>> #cpus = "" # leave to Xen to pick
> >>> #cpus = "0" # all vcpus run on CPU0
> >>> #cpus = "0-3,5,^1" # run on cpus 0,2,3,5
> >>> vcpus = 1
> >>>
> >>> vif = [ '', 'bridge=xenbr1' ]
> >>>
> >>> device_model = '/usr/lib64/xen/bin/qemu-dm'
> >>
> >> Don't need a device-model if you're not using HVM.
> >>>
> >>> disk = [ 'phy:/dev/VGvhosts/root,hda1,w',
> >>> 'phy:/dev/VGvhosts/swap,hda2,w',
> >>> 'phy:/dev/VGvhosts/tmp,hda3,w' ]
> >>> # 'phy:/dev/VGvhosts/var,hda4,w' ]
> >>>
> >>> dhcp="dhcp"
> >>>
> >>> # Set root device.
> >>> root = "/dev/hda1"
> >>>
> >>>
> >>> cdrom = "/home/admn/iso/6.2-RELEASE-i386-disc1.iso"
> >>
> >> Can't boot from CDROM if you're not using HVM.
> >>
> >>> boot = "dc"
> >>
> >> Likewise, "boot" and "root" are sort of equivalent for
> "HVM" and "PV"
> >> domains - they both say where to boot from, "boot" is for
> HVM domains,
> >> "root" is for "PV" domains (it's passed to the kernel that you're
> >> loading).
> >>>
> >>> [root@octavpc1 xen]# mcedit linux
> >>>
> >>> [root@octavpc1 xen]# cat linux
> >>> #kernel = "/boot/vmlinuz-2.6.10-xenU"
> >>> kernel = "/boot/vmlinuz-2.6.18-8.1.4.el5xen"
> >>>
> >>> # The domain build function. Default is 'linux'.
> >>> builder='linux'
> >>
> >> Correct.
> >>>
> >>> memory = 512
> >>>
> >>> name = "linux-test"
> >>
> >> That's better.
> >>>
> >>> # List of which CPUS this domain is allowed to use,
> default Xen picks
> >>> #cpus = "" # leave to Xen to pick
> >>> #cpus = "0" # all vcpus run on CPU0
> >>> #cpus = "0-3,5,^1" # run on cpus 0,2,3,5
> >>> vcpus = 1
> >>>
> >>> vif = [ '', 'bridge=xenbr1' ]
> >>>
> >>> device_model = '/usr/lib64/xen/bin/qemu-dm'
> >>
> >> Still shouldn't use device-model.
> >>>
> >>> disk = [ 'phy:/dev/VGvhosts/root,hda1,w',
> >>> 'phy:/dev/VGvhosts/swap,hda2,w',
> >>> 'phy:/dev/VGvhosts/tmp,hda3,w' ]
> >>> # 'phy:/dev/VGvhosts/var,hda4,w' ]
> >>>
> >>> dhcp="dhcp"
> >>>
> >>> # Set root device.
> >>> root = "/dev/hda1"
> >>>
> >>>
> >>> cdrom = "/home/admn/iso/6.2-RELEASE-i386-disc1.iso"
> >>> boot = "dc"
> >> And still can't boot from CDROM in PV mode.
> >>> ----------------------
> >>>
> >>>
> >>> When I do a xm create -c linux, I see the vm booting (at
> >>> least that's what
> >>> I think it's doing) and I receive an error. Here are the last
> >>> line of what
> >>> I see on my screen:
> >>> ----------------
> >>> Initializing IPsec netlink socket
> >>> NET: Registered protocol family 1
> >>> NET: Registered protocol family 17
> >>> XENBUS: Device with no driver: device/vbd/769
> >>> XENBUS: Device with no driver: device/vbd/770
> >>> XENBUS: Device with no driver: device/vbd/771
> >>> XENBUS: Device with no driver: device/vif/0
> >>> XENBUS: Device with no driver: device/vif/1
> >>> md: Autodetecting RAID arrays.
> >>> md: autorun ...
> >>> md: ... autorun DONE.
> >>> VFS: Cannot open root device "hda1" or unknown-block(0,0)
> >>
> >> Does "/dev/hda1" contain a vaild filesystem?
> >>
> >> --
> >> Mats
> >>> Please append a correct "root=" boot option
> >>> Kernel panic - not syncing: VFS: Unable to mount root fs on
> >>> unknown-block(0,0)
> >>>
> >>>
> >>> If I try to mount the logical volumes, I get:
> >>> --------------------
> >>> Using config file "./linux".
> >>> Error: destroyDevice() takes exactly 3 arguments (2 given)
> >>> ----------------------
> >>> I tried to change from hda to sda, I have also tried sda3 for
> >>> all of them
> >>> since my disk looks like this:
> >>> sda1 - / -30GB
> >>> sda2 - swap -3,5GB
> >>> sda3 - lvm - 209GB
> >>> On the lvm I have the following partitions formated as ext3:
> >>> root, var,
> >>> tmp and .... swap.
> >>>
> >>> I know I have the image of a bsd cd know (I'll make an image
> >>> of a linux
> >>> and use that instead), but it should at least boot! Right?
> >>>
> >>> So I tried a lot of Google and couldn't find an answer to my
> >>> problem. This
> >>> is my first time with xen. Can U please help me?
> >>>
> >>> Thanks in advance.
> >>>
> >>>
> >>> _______________________________________________
> >>> 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
|
Home