It seems to be fixed for me. Using hvm I can now start a 7.3-FreeBSD cd.

I hope this helps someone:
I went from kernel-xen-2.6.18-164.9.1.el5 to 
kernel-xen-2.6.18-194.8.1.el5.centos.plus.
And also updated xen(now version 3.4.3): xen-libs-3.4.3-1.el5,...

rpm -qa |grep xen
kernel-xen-2.6.18-164.9.1.el5
kmod-drbd83-xen-8.3.8-1.el5.centos
kernel-xen-devel-2.6.18-194.8.1.el5.centos.plus
kmod-drbd83-xen-8.3.5-1.el5
xen-3.4.3-1.el5
kernel-xen-2.6.18-194.8.1.el5.centos.plus
kmod-fuse-xen-2.7.4-21.el5
kernel-xen-devel-2.6.18-194.3.1.el5
xen-devel-3.4.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.3-1.el5

I used the RPMs provided from here:
http://www.gitco.de/repo/


> From: drums_...@hotmail.com
> To: a...@nirgal.de; mikemacl...@gmail.com
> Date: Tue, 20 Jul 2010 18:58:06 +0200
> CC: freebsd-xen@freebsd.org
> Subject: RE: FreeBSD DomU: Upgrade from 7.2 to 8.0
> 
> 
> Forgot this: what is currently working for me is:
> FreeBSD vpn-gateway 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct  2 
> 12:21:39 UTC 2009     
> r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
> 
> 
> 
> Do note that I tried multiple install media and it seemed that nothing above 
> 7.2 was actually working.
> 
>  
> 
> 
> 
> 
> > From: a...@nirgal.de
> > To: mikemacl...@gmail.com
> > Date: Tue, 20 Jul 2010 18:05:24 +0200
> > CC: freebsd-xen@freebsd.org
> > Subject: Re: FreeBSD DomU: Upgrade from 7.2 to 8.0
> > 
> > Hi,
> > 
> > Am 20.07.2010 um 17:42 schrieb Michael MacLeod:
> > 
> > > The XENHVM config, if I'm not mistaken, is pretty well only  
> > > supported when
> > > using an amd64 version of FreeBSD. Also, it will require some slight  
> > > changes
> > > to the config file. Specifically, the line "vif =  
> > > [ 'type=ioemu,bridge=eth0'
> > > ]" from the config file I posted earlier would have to be changed to  
> > > "vif =
> > > [ 'bridge=eth0' ]", because you aren't emulating an re NIC any  
> > > longer. The
> > > XENHVM kernel is an HVM style kernel but it loads paravirtualized NIC
> > > drivers (same with the block devices as well).
> > 
> > Thanks for the additional information. I have requested the current  
> > configuration of my DomU from my provider.
> > 
> > > Who is your provider that is using 3.3.1?
> > 
> > A small company in southern germany. They are providing me a custom  
> > solution, since no one seems to be able to provide a virtual FreeBSD  
> > of the shelf in germany. The bright side: the service is top notch.
> > Please write me off-list, if you need a contact.
> > 
> > Regards,
> > 
> > Alex
> > _______________________________________________
> > freebsd-xen@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
>                                         
> _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
                                          
_______________________________________________
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Reply via email to