virtualisation conference
by Raphaël Bauduin
Hi all,
Profoss (http://www.profoss.eu) is organising a European
virtualisation conference on
22 and 23 january in Brussels. Xen will of course be part of the
talks. Speakers related
to Xen directly are Kris Buytaert, co-author of "Virtualization with
Xen", and Frank Kohler,
who will talk of integration of virtualisation in the operating system.
Talks are not commercial but really informative. The first day is
looking at business
aspect of virtualisation, the second day looks at technical aspects.
All info about the event is at http://www.profoss.eu/events/
Participation costs are really affordable, so I hope to see you there!
Raph
16 years, 3 months
Ignore problem with hypervisor not running
by Jack Smith
Yesterday I sent a message that the hypervisor wasn't running on my system.
It is; I just get errors when I run "virsh list" without being root. Sorry.
[kizoku@natsumi ~]$ virsh list
libvir: Xen Daemon error : internal error failed to connect to xend
libvir: Xen Daemon error : got unknown HTTP error code 0
Id Name State
----------------------------------
0 Domain-0 running
[kizoku@natsumi ~]$ sudo virsh list
Password:
Id Name State
----------------------------------
0 Domain-0 running
--
Jack Smith
English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
16 years, 3 months
Re: [Fedora-xen] Routing doesn't work when I boot with the Xen kernel
by Jack Smith
I have no idea why, but the problem corrected itself overnight. Something,
either in Fedora, the router, Comcast or somewhere must have run and fixed
the problem. I have no idea how.
On Jan 8, 2008 8:21 AM, Dustin Henning <Dustin.Henning(a)prd-inc.com> wrote:
> When the xend service starts, it creates bridges and virtual
> interfaces attached to those bridges. I am not so familiar with it to
> tell
> you how to correct your problem on a permanent basis, but I can tell you
> that perhaps the network script isn't preserving your routes. Check your
> routes and see if a default route to the Linksys still exists. It also
> seems to me like F8 may use a different default xen network script, so
> depending on what you want to do, you many need to change the network
> script
> in xen's config file. This advice may be legacy, as I know Fedora's
> implementation gets more and more custom with each release, and I
> generally
> fall back on old xen configuration techniques in spite of that, so this
> may
> not be the route you want to take.
> Dustin
>
> From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com]
> On Behalf Of Jack Smith
> Sent: Monday, January 07, 2008 22:40
> To: fedora-xen(a)redhat.com
> Subject: [Fedora-xen] Routing doesn't work when I boot with the Xen kernel
>
> I have a choice of kernels to boot with in Grub,
> 2.6.21-2952.fc8xen
> 2.6.23.9-85.fc8
> 2.6.23.1-42.fc8
>
> As far as I can see, I have networking set up the same on all three.
> (Besides, wouldn't they use the same configuration files at boot time?) My
> problem is, when I boot with the xen kernel, I can't get out through my
> router. I can ping everything on my eth0 or eth1 networks, just not go
> through my eth0 Linksys router. The only difference I've been able to see
> is that something called "peth0" uses the same card as the NIC my router
> is
> on. Is this getting in the way somehow?
> eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
> inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:10 errors:0 dropped:0 overruns:0 frame:0
> TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:494 (494.0 b) TX bytes:6566 (6.4 KiB)
>
> eth1 Link encap:Ethernet HWaddr 00:17:31:01:D0:20
> inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::217:31ff:fe01:d020/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:29 errors:0 dropped:0 overruns:0 frame:0
> TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2412 (2.3 KiB) TX bytes:8491 (8.2 KiB)
> Interrupt:23 Base address:0xe000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8504 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8504 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:10008668 (9.5 MiB) TX bytes:10008668 (9.5 MiB)
>
> peth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
> inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:53 errors:0 dropped:0 overruns:0 frame:0
> TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:5414 (5.2 KiB) TX bytes:14547 (14.2 KiB)
> Interrupt:18
>
> virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:5156 (5.0 KiB)
>
> Thanks,
>
> --
> Jack Smith
>
> English doesn't borrow from other languages -- English follows other
> languages down dark alleys and takes what it wants.
>
>
>
--
Jack Smith
English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
16 years, 3 months
Routing doesn't work when I boot with the Xen kernel
by Jack Smith
I have a choice of kernels to boot with in Grub,
2.6.21-2952.fc8xen
2.6.23.9-85.fc8
2.6.23.1-42.fc8
As far as I can see, I have networking set up the same on all three.
(Besides, wouldn't they use the same configuration files at boot time?) My
problem is, when I boot with the xen kernel, I can't get out through my
router. I can ping everything on my eth0 or eth1 networks, just not go
through my eth0 Linksys router. The only difference I've been able to see
is that something called "peth0" uses the same card as the NIC my router is
on. Is this getting in the way somehow?
eth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
inet addr:192.168.1.151 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:494 (494.0 b) TX bytes:6566 (6.4 KiB)
eth1 Link encap:Ethernet HWaddr 00:17:31:01:D0:20
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::217:31ff:fe01:d020/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2412 (2.3 KiB) TX bytes:8491 (8.2 KiB)
Interrupt:23 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8504 errors:0 dropped:0 overruns:0 frame:0
TX packets:8504 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10008668 (9.5 MiB) TX bytes:10008668 (9.5 MiB)
peth0 Link encap:Ethernet HWaddr 00:17:31:01:C8:A8
inet6 addr: fe80::217:31ff:fe01:c8a8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:53 errors:0 dropped:0 overruns:0 frame:0
TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5414 (5.2 KiB) TX bytes:14547 (14.2 KiB)
Interrupt:18
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:5156 (5.0 KiB)
Thanks,
--
Jack Smith
English doesn't borrow from other languages -- English follows other
languages down dark alleys and takes what it wants.
16 years, 3 months
Are 64bit Intel Core 2 Quad fedora 8 supported?
by George Refseth
The 64 bit xen host kernel are unstable (timer/scheduling issue?)
So I wonder if this is supported or not. Another Fedora 8 x86_64
installation on
an Intel Core 2 Duo seems to run flawlessly, except it is running on a
laptop,
and not meant for server use.
Attached are smolt output.
I would be grateful for any input, this was meant to be a system where
multiple
services should run (several 64bit F8's) serving dns, web and mail, and
replace
at least two current lumps of hardware..
regards,
George
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
16 years, 3 months
BUG: rawhide installer does not autoload xenblk/xennet modules
by Pasi Kärkkäinen
Hello!
I just tried to install rawhide/development to a xen domU with virt-manager,
and it seems current kernel (or xen drivers?) has a bug that prevents
anaconda/installer from autoloading the needed drivers..
virt-install -n test -r 512 --vcpus=1 -f /dev/vg0/test_disk1 --vnc -p -b xenbr0
-l "http://mirror/fedora.redhat.com/pub/fedora/linux/development/i386/os"
starts up the console/vnc window, boots up linux and the installer, lets me
choose language and keyboard type, and then says:
"No driver found"
"Unable to find any devices of the type needed for this installation type."
"Would you like to manually select your driver or use a driver disk?"
And at the moment anaconda is broken for manually picking drivers, so
installation doesn't work at all when using xen :) (this is a separate bug)
-- Pasi
16 years, 3 months
Fedora 8 DomU (i386) does not work on Fedora 8 (x86_64) host
by Felix Schwarz
Hi,
I'm using Xen since Fedora Core 6. My Dom0 runs the latest version of
Fedora 8. Currently, I can install a Fedora 8 i386 DomU. The installation
always hangs after formatting the virtual hard drive. The only message is
"Please wait... This may take a few minutes" (from memory, translated from
German). Unfortunately, this message appears not for some minutes but stays
"forever" (at least 30 minutes).
My computer is reasonably fast (AMD X2) with plenty of RAM (4 GB). With
Fedora 8 (x86_64) this messages is only visible for some seconds. There is
no difference if I do install F8 i386 as HVM or PV domain.
One thing I noticed is that I did not manage to install Fedora 8 using QEMU.
Did anyone experience similar issues? I suspect, my local Fedora
installation repository may be faulty although all packages are fine
(checked with "rpm --checksig *") and I regenerated the repodata multiple
times.
Any hints? Thank you very much.
fs
16 years, 3 months
Re: [Fedora-xen] network speed on hvm guests
by Pasi Kärkkäinen
On Fri, Jan 04, 2008 at 11:57:09AM -0500, Dustin Henning wrote:
> I was reading an article about Windows PE 2.0 in virtual
> environments, and apparently Windows PE 2.0 is based on Vista, which doesn't
> have a driver for the default NIC used by VMWare. The suggested solution is
> to use a different virtual NIC (a gigabit one). Obviously Xen isn't VMWare,
> and on top of that, I am not trying to run Windows PE 2.0, or even Vista.
> However, I had long wondered but never asked this question:
> Does Xen have any virtual NICs other than the two mentioned in the
> hvm example files in /etc/xen? More importantly, does it matter, for
> instance, will Xen or Windows limit the response time or throughput to
> 100MB/s levels in an hvm environment if a 100MB/s virtual NIC is used? I
> don't see why it would, but then again, I don't see why SATAII hard drives
> running on controllers in IDE mode are slowed to IDE speeds, so I wouldn't
> be surprised if it did, and I am hoping someone can tell me. Thanks,
> Dustin
>
Xen HVM guests see _emulated_ hardware. Emulated NIC, Emulated ide/disk
controller, etc.
Emulation is slow.
You need to have/install paravirtualized (=optimized) drivers that "bypass"
the whole emulation layer and talk directly to Xen.. this way you can get
good performance.
Xen includes paravirtualized drivers ("unmodified drivers") for linux HVM
guests.
People are working with free/opensource paravirtualized drivers for Windows
HVM guests atm, but they're not really usable/stable yet.
XenEnterprise, VirtualIron, and Novell SLES have Windows HVM pv drivers
available.. if you buy those products.
-- Pasi
16 years, 3 months
network speed on hvm guests
by Dustin Henning
I was reading an article about Windows PE 2.0 in virtual
environments, and apparently Windows PE 2.0 is based on Vista, which doesn't
have a driver for the default NIC used by VMWare. The suggested solution is
to use a different virtual NIC (a gigabit one). Obviously Xen isn't VMWare,
and on top of that, I am not trying to run Windows PE 2.0, or even Vista.
However, I had long wondered but never asked this question:
Does Xen have any virtual NICs other than the two mentioned in the
hvm example files in /etc/xen? More importantly, does it matter, for
instance, will Xen or Windows limit the response time or throughput to
100MB/s levels in an hvm environment if a 100MB/s virtual NIC is used? I
don't see why it would, but then again, I don't see why SATAII hard drives
running on controllers in IDE mode are slowed to IDE speeds, so I wouldn't
be surprised if it did, and I am hoping someone can tell me. Thanks,
Dustin
16 years, 3 months
RE: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?
by Christian Lahti
Hi Mark:
Thank you very much for your response, I did indeed read the original poster as Dale by mistake :) So what you are saying makes perfect sense to me and sounds like exactly what we are after, I will have 3 vlans to bridge myself ultimately. My next question is the relative merits of RHEL5.1 as compared to Fedora 8. Obviously I would prefer the stable enterprise release rather than bleeding edge Fedora, but has fully virtualized windows performance been fixed in this release? At any rate I am looking forward to getting this up and running tomorrow!
/Christian
________________________________
From: Mark Nielsen [mailto:mnielsen@redhat.com]
Sent: Sat 12/1/2007 3:19 PM
To: Christian Lahti
Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?
hmm, did you mean "Hi Mark" ??
I have 8 Dell 2950s running RHEL 5.1 (new libvirt with that funky NAT
they added). I have 4 NICs in each; 2 copper, 2 fiber. I bond the 2
copper (eth0 and eth1) and call it bond0. bond0 carries my "private" IP
for cluster suite communications on the dom0 (physical) cluster.
Then I bond eth2 and eth3 (fiber) in to bond1. I lay down the public
network for the dom0 cluster on bond1.100 (for example, that would be
VLAN 100). I also add many (up to 10 or so now) VLANs on bond1
(bond1.20, bond1.21, bond1.22, etc). Then I create xen bridges to each
of these bond/VLAN devices. This allows me to put any particular VM on
any particular (or combination up to 3) of these xen bridged bonded VLAN
device.
My document explains, in detail, how to do all of this :) The only added
step is that I have to "undefine" (virsh net-undefine default) the
default network that the new libvirt creates (virbr0). Even with this
new NAT thing they added, I've been told (by our devs) that the
preferred way to do static network configurations is with the method I
lay out. NAT is more for dynamic networks (cable modems, dial-up, wifi,
etc).
I'm pretty sure there weren't any significant changes in Fedora 8 (we've
dropped the word "core" now, btw) that don't exist in RHEL 5.1 with
respects to the network. 5.0 -> 5.1 is when that NAT change came down
the pipe.
Mark
p.s. I'm happy to answer any other questions you may have about my
document. I'm quite certain that, if you follow it, you'll have what
you're looking for.
Christian Lahti wrote:
> Hi Dale:
>
> I work with David who posted the original question to the mailing
> list. I think we need to give a bit more background info on what we
> are trying to do. We are running a mixed environment of mostly CentOS
> 3, 4and 5, we do have a few windows servers and XP systems as well.
> We are looking to virtualize all these platforms. Normally we have a
> bonded pair of NICs for the physical hosts, we were able to get this
> running using CentOS 5 x86_64 with no problems, the guest machines use
> the bonded pair in bridged mode as expected after a bit of tweaking.
> The biggest issue we found with EL5 is that windows guest performace
> is dismal at best, hence our decision to have a look at Fedora Core 8
> x86_64. I am happy to report that performance for all of our guest
> platforms is *very* good with FC8, but it seems that libvirt changed
> the way networking is setup for Xen. The default NAT configuration is
> pretty useless for production server environment. Thanks to the
> mailing list we are now able to bridge a single NIC on FC8 (like eth0
> for example), but we cannot figure out how to get a bridge for bond0
> (comprised of eth0 and eth1) defined and available to Xen. All the
> tweaks that worked find on EL5 have not worked so far on FC8. I am
> going to review your document tomorrow and give it a try, but any idea
> on whether your methodology will work on FC8 and libvirt? I am
> willing to blow a Sunday to get this worked out once and for all :)
>
> Basically we are after good performance on both para and fully
> virtualized guests using a bonded pair of GB NICs for speed and
> redundancy. If this can be achieved with enterprise linux then that
> would be preferable, but we will go FC8 if the bonding thing can be
> sorted out. By the way Xensource 4.x looks to be a respin of RHEL5
> and has pretty good performance but their free version is limited to
> 32bit (and hence 4GB ram). Adding the clustering failover is the next
> step of course :)
>
> Thanks again for the help so far.
>
> /Christian
>
>
>
> >>>>>>>>>>>
> just FYI for the list, I have a how-to for a bonded and VLAN tagged network.
>
> http://www.certifried.com
>
> ODT and PDF formats available.
>
>
> It might not be the best way, but I've sent it out to my colleagues
> several times and have never received any negative feedback.
> Mark
>
>
>
> Dale Bewley wrote:
>
>
> I haven't done bonding, but you should be able to bond them and then compose a bridge on top of this bonded device I would think.
>
> --
> Dale Bewley - Unix Administrator - Shields Library - UC Davis
> GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
>
> --
> Fedora-xen mailing list
> Fedora-xen redhat com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
> ****************************************************************************
> Checked by MailWasher server (www.Firetrust.com)
> WARNING. No FirstAlert account found.
> To reduce spam further activate FirstAlert.
> This message can be removed by purchasing a FirstAlert Account.
> ****************************************************************************
>
> ------------------------------------------------------------------------
>
> --
> Fedora-xen mailing list
> Fedora-xen(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
16 years, 3 months
