[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-users] Attempt to set up Libvirt 0.7.7 & Xen 4.0 Dom0 (2.6.32.13) on top of F13 RC2
- To: xen-users@xxxxxxxxxxxxxxxxxxx
- From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
- Date: Mon, 24 May 2010 10:01:20 -0700 (PDT)
- Delivery-date: Mon, 24 May 2010 10:04:26 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=oWoT4fibFXy8Bmmxp2CZv5x85T2NiFAaludD4BzAshNnk/MqK/McbdMrAS335uYbgKJ02TriHh0zq/YuNt2mMcBtGzggqlIGK2jJCa5IFvYqjFFI2XoQHa6+56BoGfedmHAWG5huNyRg+zyhTXBLKvG0+V9pbFclMhm+lzisTAg=;
- List-id: Xen user discussion <xen-users.lists.xensource.com>
The most recent yum update has been run.
Installed Xen 4.0 and Libvirt like on F12. Via my experience xend will hang for 5-7 min at startup and xen managed bridging will fail as well. This behavior stays the same under either 2.6.32.13 or 2.6.33.3 pvops kernels. At the same time PV guests might be unable to obtain IP via interface virbr0. Ubuntu Lucid official xenified installer fails with DHCP request been sent to virbr0 under 2.6.32.13 kernel.
I've checked NAT bridge detection at Libvirt 0.7.1 & Xen 4.0 (2.6.32.13) on top of F12 and at Libvirt 0.7.0 & Xen 4.0 (2.6.32.13) on top of Ubuntu 10.04 Server. Looks like only RH's PV guests happily detect virbr0 during install and runtime ( coming out of the LAN to the Net). Ubuntu 10.04 xenified PV installer and any OSOL (<= 134) requires old style network bridge to Dom0.
In
particular on F13 , i have to disable all xen managed network bridging except
(network-script /bin/true)
# chkconfig NetworkManager off
# chkconfig network on
Manually create a bridge
# service network start
Boris.
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
