Discussion of the installation and of use of Xen.

Error during booting Dom0

Hi all,
I am newbie to Xen.

I am facing a problem in booting Dom0 OS.

I have FC8 OS which i want as Dom0. Its kernel is having by default Dom0
support. Xen is v 3.4 latest build from source.

So when I boot up the machine with Xen hypervisor i get some error on boot
screen.

Errors:
---------------------------------------------------------------------
(XEN) Cannot load bzImage v2.06 at least v2.08 is required.

(XEN) Xenoproof:Initialization failed . No APIC

(XEN) I/O virtualization disabled.
************************************************************
Panic on CPU0
Could not set up Dom0 guest OS
**************************************************************
----------------------------------------------------------------------

I have not captured the entire screen as i am not able to do it. I just
wrote down few messages.

My grub entry:

title Xen 3.4 / Fedora (2.6.23.1-42.fc8)
root (hd0,1)
kernel /xen-3.4.gz
module /vmlinuz-2.6.23.1-42.fc8 ro root=/dev/VolGroup00/LogVol00
rhgb quiet
module /initrd-2.6.23.1-42.fc8.img

Does any one is having any idea about this.

Thanks
Vipul.

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

headers

Fajar A. Nugraha | 1 Dec 07:04

Re: Problem creating vm with two nics

On Mon, Nov 30, 2009 at 8:53 PM, Martin Aceto <maceto <at> backing-online.com> wrote:

> Probe with one alone Nic
>
> /etc/xen/scripts/network-bridge-wrapper
>
> #!/bin/sh
> dir=$(dirname "$0")
> "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
>
> but make the same think, not boot.

If it didn't work with one NIC and network-bridge-wrapper, then most
likely the problem is in the wrapper. Perhaps some things have changed
from previous versions. You might have better luck setting up bridges
manually or using OS scripts (like
/etc/sysconfig/network-scripts/ifcfg-* on RHEL/Centos) and comment out
xen's network-script on xend-config.sxp

> vif = [ 'ip=10.10.10.150,mac=00:16:3e:11:c3:7c,bridge=xenbr0',
> 'ip=192.168.10.15,mac=00:16:3e:24:87:ae,bridge=xenbr1' ]

Errr... you DID remove the vif entry referencing xenbr1 while testing
it with only one bridge, right?

Another thing to check, make sure udevd is running on dom0. Sometimes
it's dead for unknown reasons.

--

-- 
Fajar

headers

Fajar A. Nugraha | 1 Dec 07:06

Re: Updating DomUs kernels

On Mon, Nov 30, 2009 at 9:36 PM, Martin Gombac( <martin <at> isg.si> wrote:

> kernel = "/bootvirts/vmlinuz-2.6.26-2-xen-amd64"
> ramdisk = "/bootvirts/initrd.img-2.6.26-2-xen-amd64"
> disk = ['drbd:r0,sda1,w']
> root = "/dev/sda1 ro"
>
> What i'm wondering now is, how the kernel updating will work or how it's
> supposed to work? User of this virtual machine will be able to update the
> kernel on drbd device (in his virtual machine) but not in /bootvirts/ on
> Dom0, as it's not accessible from within virtual machine. Or am I mistaken?

... and that is exactly why by default RHEL/Centos uses pygrub :)
With pygrub/pvgrub, domU kernel is located on domU filesystem, so that
users can update it themselves.

--

-- 
Fajar

headers

Fajar A. Nugraha | 1 Dec 07:17

Re: 32bit domUs

On Tue, Dec 1, 2009 at 3:33 AM, Pasi Kärkkäinen <pasik <at> iki.fi> wrote:
> On Mon, Nov 30, 2009 at 10:20:29AM -0500, Robbie A. Garrett wrote:
>>    Hey all,
>>
>>    I have need to boot 32bit domu's on a amd64 system.  I was able to deploy
>>    a 32bit image but the kernel is still 64bit.  I have a feeling in my .cfg
>>    file for the domU I need to specify a 32bit kernel.  Is this correct?
>>

Most applications can run fine with 64bit kernel - 32bit userland.

>
> Yes, it's correct.
>
> Unless you use pygrub/pvgrub to load the kernel from domU filesystem.

To paraphrase that a little, you can run 32bit PV domU kernel on top
of 64bit hypervisor. Where the kernel located depends on domU setup,
can be in dom0 (thus specified in domU config file) or within domU
filesystem (when using pygrub/pvgrub).

--

-- 
Fajar

headers

Tapas Mishra | 1 Dec 09:11

Re: Need advice regarding distro

I had a lot of such problems i m not an expert user but by reading on
threads on this community and asking questions I learnt a lot I will
suggest you to use CentOS I have tested here 2 Dell Laptops and three
separate machines OpenSuse,Debian,Ubuntu Fedora and now CentOS .
My experience with CentOS is good for Xen since some or the other way
I got some sort of error on my machines right now I am still compiling
a Dom0 kernel along with Xen on Debian machine.
On my latest machine in spite of the errors CentOS was able to work.

On Tue, Dec 1, 2009 at 2:39 AM, Dana Rawding <dana <at> twc-inc.net> wrote:
> Hi All,
>
> I need some advice.  I have been running Xen under Ubuntu LTS 8.0.4 for about 18 months.  The original
install gave me the 2.6.24-19-xen kernel.
> There were a couple of updates and all my machines are currently running 2.6.24-23-xen.  Since Ubuntu
decided to go with KVM I imagine that there will be no further updates.
>
> Recently I had read that in the future Remus is going to be added to the kernel.  HA is very desirable for me
as I have a number of HA web servers that I handle with load balancing in front of virtualized images spread
over multiple servers.  The addition of synchronized failover images would be huge!  So I started
looking around at other distros that are going to continue to support Xen.  I downloaded the latest
OpenSuSE and installed on a spare HP DL380.  I was able to get it up and running on 2.6.31.5-0.1-xen.
 After testing for a few days I decided to start upgrading my production machines.
>
> To take a step back for a moment, my server farm consists of mostly HP DL380 G3's with 8 GB of RAM and dual 3.06
GHz Xeons.  I also have a couple of HP DL580 with 32 GB RAM and Quad Xeons.  While this gear is not the latest
and greatest they are real workhorses and I have a lot of them.  They run mostly mail, web, dns, etc.  No
desktops or Windows so PV is fine.
>
> So I decided to upgrade one of the DL580's.  The install seems to go OK but upon restart it continuously
hangs when bringing up the BR1 interface.  I installed the standard kernel and the interfaces come up
fine.  Furthermore I added an additional gigabit Broadcom based HP Ethernet card.  I got it configured
as eth2 and again it works fine with the non Xen kernel.  Even if I disable the onboard eth1 and assign br1 to
eth2 it continues to hang on boot.  Frustrated after two days of messing around I installed SuSE on a brand
new IBM x3500 M2 w/ dual Xeon 2.66 GHz X5550 4C's.  Again the install went fine.  However almost daily the
box just completely hangs.  I can't seem to find any log entries to figure out why this is happening.  I
can create a hang by just untarring a large file in either the DomU or a DomO.  Plenty of memory and free
processors so I don't know why it continues to die.
>
> As you can guess my current experience with SuSE has left a bad taste in my mouth on both old and new hardware.
 I was about to download Fedora and go it again but before spending the time I thought I'd ask the opinion of
the list as to what they would do/recommend.  My gut tells me to just bit the bullet and start compiling my
own kernels and stay with Ubuntu.  Ideas, comments, suggestions?
>
> Thanks,
> Dana
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users
>

--

-- 

http://www.abhitech.com

headers

Tapas Mishra | 1 Dec 09:28

Re: Updating DomUs kernels

> ... and that is exactly why by default RHEL/Centos uses pygrub :)
> With pygrub/pvgrub, domU kernel is located on domU filesystem, so that
> users can update it themselves.
I didnt get that domU filesystem you mean to say in the installed guest OS

headers

Martin Gombac( | 1 Dec 09:30

Re: Updating DomUs kernels

Hi,

i don't think CentOS 5.4 pvgrub/pygrub support drbd disk which is 
essential for my HA cluster with non interruptive failover. Will look 
into it.

Regards,
M.

Fajar A. Nugraha wrote:
> On Mon, Nov 30, 2009 at 9:36 PM, Martin Gombac( <martin <at> isg.si> wrote:
> 
>> kernel = "/bootvirts/vmlinuz-2.6.26-2-xen-amd64"
>> ramdisk = "/bootvirts/initrd.img-2.6.26-2-xen-amd64"
>> disk = ['drbd:r0,sda1,w']
>> root = "/dev/sda1 ro"
>>
>> What i'm wondering now is, how the kernel updating will work or how it's
>> supposed to work? User of this virtual machine will be able to update the
>> kernel on drbd device (in his virtual machine) but not in /bootvirts/ on
>> Dom0, as it's not accessible from within virtual machine. Or am I mistaken?
> 
> ... and that is exactly why by default RHEL/Centos uses pygrub :)
> With pygrub/pvgrub, domU kernel is located on domU filesystem, so that
> users can update it themselves.
>

headers

Tapas Mishra | 1 Dec 09:35

Re: 32bit domUs

These config files were suggested to me by Pasi Kärkkäinen you can
check them I am posting here for reference.
http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.4-pvops_dom0-x86_64
http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.5-pvops_dom0-x86_32
I am right now working to get a Debian system working for Dom0 kernel
if you get some success let us know here.

On Mon, Nov 30, 2009 at 8:50 PM, Robbie A. Garrett
<RGarrett <at> hostourweb.com> wrote:
> Hey all,
>
> I have need to boot 32bit domu's on a amd64 system.  I was able to deploy a
> 32bit image but the kernel is still 64bit.  I have a feeling in my .cfg file
> for the domU I need to specify a 32bit kernel.  Is this correct?
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users
>

--

-- 

http://www.abhitech.com

headers

Jingyun He | 1 Dec 11:43

can not remove windows vps from hard disk

Hello all,
I have a problem with removing the LVM partition that is used by windows vps.
When I tried to remove the LVM partition, I got the error "Can't
remove open logical volume ."

So I run parted /dev/VolGropu00/xxx
then executed "rm 1",

I got the Error: Partition /dev/mapper/VolGroup00-xxxp1 is being used.
You must unmount it before you modify it with Parted.

Anyone can tell me how to unmount it?

Thanks.

headers

Taschik, Daniel | 1 Dec 11:48

Re: can not remove windows vps from hard disk

Hello,

you can unmount it with 

umount /dev/VolGropu00/xxx

or type in mount and look what it tells you how your device is called.

Cheers

Daniel

On 01.12.2009, at 11:43, Jingyun He wrote:

> Hello all,
> I have a problem with removing the LVM partition that is used by windows vps.
> When I tried to remove the LVM partition, I got the error "Can't
> remove open logical volume ."
> 
> So I run parted /dev/VolGropu00/xxx
> then executed "rm 1",
> 
> I got the Error: Partition /dev/mapper/VolGroup00-xxxp1 is being used.
> You must unmount it before you modify it with Parted.
> 
> Anyone can tell me how to unmount it?
> 
> Thanks.
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users

123	February 2012
351	January 2012
323	December 2011
632	November 2011
570	October 2011
544	September 2011
612	August 2011
668	July 2011
630	June 2011
655	May 2011
473	April 2011
671	March 2011
761	February 2011
638	January 2011
494	December 2010
560	November 2010
643	October 2010
742	September 2010
713	August 2010
791	July 2010
1196	June 2010
1124	May 2010
1073	April 2010
975	March 2010
890	February 2010
864	January 2010
670	December 2009
817	November 2009
872	October 2009
732	September 2009
782	August 2009
765	July 2009
914	June 2009
934	May 2009
747	April 2009
782	March 2009
876	February 2009
1040	January 2009
594	December 2008
850	November 2008
730	October 2008
983	September 2008
1023	August 2008
987	July 2008
1206	June 2008
1015	May 2008
1061	April 2008
894	March 2008
1131	February 2008
907	January 2008
718	December 2007
779	November 2007
747	October 2007
583	September 2007
754	August 2007
777	July 2007
1134	June 2007
962	May 2007
928	April 2007
1124	March 2007
1122	February 2007
1388	January 2007
1005	December 2006
980	November 2006
1043	October 2006
968	September 2006
1009	August 2006
854	July 2006
1160	June 2006
963	May 2006
1138	April 2006
986	March 2006
982	February 2006
1312	January 2006
932	December 2005
727	November 2005
646	October 2005
805	September 2005
809	August 2005
738	July 2005
686	June 2005
605	May 2005
480	April 2005

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31