Date: Tue, 20 Jul 2010 14:03:20 +0200 From: G VM <drums_gvm@hotmail.com> To: <mikemacleod@gmail.com> Cc: freebsd-xen@freebsd.org, got.andras@deployis.eu Subject: RE: FreeBSD DomU: Upgrade from 7.2 to 8.0 Message-ID: <SNT130-w29A1581E8B7BFE818925E91A00@phx.gbl> In-Reply-To: <AANLkTilw-mdsD8B8IRZc93PbiXlJEdn9hJZDL3BbOp3M@mail.gmail.com> References: <81AF01BF-D5D9-4F61-89FC-E8399A1475CD@nirgal.de>, <4C457FD9.4080900@deployis.eu> <3ABD17AA-B2D2-4456-9A83-0AAED0D16DAE@nirgal.de>, <SNT130-w513D4DD1AA0109E1D02CE091A00@phx.gbl>, <AANLkTilw-mdsD8B8IRZc93PbiXlJEdn9hJZDL3BbOp3M@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: mikemacleod@gmail.com Date: Tue=2C 20 Jul 2010 07:53:04 -0400 Subject: Re: FreeBSD DomU: Upgrade from 7.2 to 8.0 To: drums_gvm@hotmail.com CC: alex@nirgal.de=3B got.andras@deployis.eu=3B freebsd-xen@freebsd.org If you're booting the XEN kernel=2C it's going to need to be running in par= avirtualized mode. It lacks drivers for non-XEN devices. Also=2C I have fou= nd the XEN kernel running in paravirtualized mode to be nowhere near stable= enough for production use. I have used 8.0 with the GENERIC kernel in seve= ral domUs (running on Xen 3.4.2 and 4.0) successfully. This config file will work for an 8.0 box: # Name of the domU name =3D "freebsd-01" # HVM options kernel =3D "/usr/lib/xen/boot/hvmloader" device_model =3D "/usr/lib64/xen/bin/qemu-dm" builder =3D 'hvm' # Virtual hardware configuration vcpus =3D 1 memory =3D 512 disk =3D [ 'phy:/dev/SystemDisks/freebsd-01.root=2Chda=2Cw' ] vif =3D [ 'type=3Dioemu=2Cbridge=3Deth0' ] # Console and other options serial =3D 'pty' vfb =3D [ 'vnc=3D1=2Cvncdisplay=3D1' ] On Tue=2C Jul 20=2C 2010 at 7:45 AM=2C G VM <drums_gvm@hotmail.com> wrote: > From: alex@nirgal.de > To: got.andras@deployis.eu > Date: Tue=2C 20 Jul 2010 13:31:48 +0200 > CC: freebsd-xen@freebsd.org > Subject: Re: FreeBSD DomU: Upgrade from 7.2 to 8.0 > > Hello=2C > > Am 20.07.2010 um 12:52 schrieb G=F3t Andr=E1s: > > > How's your domU config file for xen? > > Up until 7.2 i have used the GENERIC Kernel and never built one of my > own=2C because there was no need. But as 7.3 or 8.0 will not boot up > with their GENERIC Kernels (tested with the Live-DVD=2C error described > in my first mail)=2C i think i have to built a custom kernel. > > I plan to use the config from > > /usr/src/sys/i386/conf/XEN > > You can find it there: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/conf/XEN?rev=3D1.9.= 2.1=3Bcontent-type=3Dtext%2Fplain=3Bonly_with_tag=3DRELENG_8_0 > > Note: i just want to use hvm-virtualization=2C paravirtualization is not > necessary. > > Alex_______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe=2C send any mail to "freebsd-xen-unsubscribe@freebsd.org" I had/have the exact same issue. I always used hvm with FreeBSD 7.2 >From the moment I upgraded to 7.3 or 8.0=2C I get a kernel panic. Even the install cd does not boot for 7.3 or 8.0. I did not fixed this yet. I would think that this is happening since there = is some virtual stuff included in the kernel by default now and this was no= t there in 7.2 Maybe you can just disable hvm or something in the kernel config. As IIRC w= ith HVM the OS is not aware that it is virtualised. Please let me know if you find a solution! Greetings! _________________________________= ______________ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe=2C send any mail to "freebsd-xen-unsubscribe@freebsd.org" I use a config with HVM(just like the one above). There are virtualization = extensions on the cpu and those are enabled. (do note that I am using an AM= D chip). It just does not run 8.0 and 7.3(nor the 64 bit nor the 32bit cd). 7.2 is running very stable for me. So I would expect that this wont fix this issue. Greetings! =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SNT130-w29A1581E8B7BFE818925E91A00>