Date: Tue, 20 Jul 2010 18:55:13 +0200 From: G VM <drums_gvm@hotmail.com> To: <alex@nirgal.de>, <mikemacleod@gmail.com> Cc: freebsd-xen@freebsd.org Subject: RE: FreeBSD DomU: Upgrade from 7.2 to 8.0 Message-ID: <SNT130-w46C74503D5DFAD3C6C0E7691A00@phx.gbl> In-Reply-To: <F6FAB5B9-8E53-4C42-A44E-15F39FFCE3FE@nirgal.de> 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>, <32DCF89B-7EE7-4B15-A3DA-334A7AEBC53B@nirgal.de>, <SNT130-w21B62E6832D0BC46E8E70391A00@phx.gbl>, <AANLkTilbRV1tXYxBOr9LUgy9ASS5cvQwg5_3FNpJdrAN@mail.gmail.com>, <F6FAB5B9-8E53-4C42-A44E-15F39FFCE3FE@nirgal.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is my config file with which it fails: name =3D "prod1" uuid =3D "25c2ae8fad757300339f0a8dd0adcba0" maxmem =3D 500 memory =3D 500 vcpus =3D 1 builder =3D "hvm" kernel =3D "/usr/lib/xen/boot/hvmloader" boot =3D "c" pae =3D 1 #acpi =3D 1 #apic =3D 1 on_poweroff =3D "destroy" on_reboot =3D "restart" on_crash =3D "restart" device_model =3D "/usr/lib64/xen/bin/qemu-dm" sdl =3D 0 vnc =3D 1 # vncunused =3D 0 vncdisplay =3D "0" disk =3D [ "file:/var/lib/xen/images/freebsd72-prod-new.img=2Chda=2Cw"=2C "= phy:/dev/loop0=2Chdc:cdrom=2Cr"=2C "phy:/dev/loop1=2Chdd:cdrom=2Cr" ] serial =3D "pty" vif=3D['bridge=3Dbr0=2Cmac=3D00:16:ef:45:12:22'] =20 I wonder if changing the last line would fix this. Using centos 5 with these versions: rpm -qa | grep xen kernel-xen-2.6.18-164.9.1.el5 xen-3.4.2-2.el5 kmod-drbd83-xen-8.3.5-1.el5 xen-devel-3.4.2-2.el5 kmod-fuse-xen-2.7.4-21.el5 kernel-xen-devel-2.6.18-194.3.1.el5 kernel-xen-2.6.18-194.3.1.el5 kernel-xen-devel-2.6.18-164.9.1.el5 xen-libs-3.4.2-2.el5 Linux hostname 2.6.18-164.9.1.el5xen #1 SMP Tue Dec 15 TIME TIMEZONE 2009 x= 86_64 x86_64 x86_64 GNU/Linux processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 67 As far as I have read this cpu should work. Any ideas on how to fix this issue? > From: alex@nirgal.de > To: mikemacleod@gmail.com > Date: Tue=2C 20 Jul 2010 18:05:24 +0200 > CC: freebsd-xen@freebsd.org > Subject: Re: FreeBSD DomU: Upgrade from 7.2 to 8.0 >=20 > Hi=2C >=20 > Am 20.07.2010 um 17:42 schrieb Michael MacLeod: >=20 > > The XENHVM config=2C if I'm not mistaken=2C is pretty well only =20 > > supported when > > using an amd64 version of FreeBSD. Also=2C it will require some slight = =20 > > changes > > to the config file. Specifically=2C the line "vif =3D =20 > > [ 'type=3Dioemu=2Cbridge=3Deth0' > > ]" from the config file I posted earlier would have to be changed to =20 > > "vif =3D > > [ 'bridge=3Deth0' ]"=2C because you aren't emulating an re NIC any =20 > > longer. The > > XENHVM kernel is an HVM style kernel but it loads paravirtualized NIC > > drivers (same with the block devices as well). >=20 > Thanks for the additional information. I have requested the current =20 > configuration of my DomU from my provider. >=20 > > Who is your provider that is using 3.3.1? >=20 > A small company in southern germany. They are providing me a custom =20 > solution=2C since no one seems to be able to provide a virtual FreeBSD =20 > of the shelf in germany. The bright side: the service is top notch. > Please write me off-list=2C if you need a contact. >=20 > Regards=2C >=20 > 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" =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SNT130-w46C74503D5DFAD3C6C0E7691A00>