Possible to delegate hardware to domU?
by Arik Raffael Funke
Hi,
is it possible to hide hardware from dom0 and delegate it to a domU with
the out-of-the-box Fedora xen? I.e. with pciback. I would like to
delegate a network interface to one of my domU's. Can anybody confirm
either that it is or that it is not possible?
Thanks.
- Arik
16 years, 9 months
easy way to configure domU
by Asrai khn
Hi I am wondering is there an easy way to configure domU (vm) quickly, atm
we are using eg LV (Logical Volumes) to storge root, var and swap for VM and
then using
disk = [ 'phy:vg/myvmdisk1,sda1,w', ... ,... ] to launch it.
We takes the tar gunzip of file system of root, var of currently running vm
and when need arrives we just have to created LVs and untar the achieves
and launch the new vm with very little changes.
Only one problem in this approach is that we get little outdated vm which
need to update using 'yum'. So is there a way to start new vm fast and using
currently updated running vm file system?
Thanks. Askar.
16 years, 9 months
Paravirtualized on FC5/6 or CentOS4/5 with 64bit hypervisor?
by thewird
I have 32bit FC7 installed and I replaced the hypervisor (xen.gz) with
its 64bit version by extracting the RPM in order to allow me to see my
28GB of ram. Everything works fine and I can install both 32bit and
64bit FC7's paravirtualized. However, when I try to install (32bit)
FC5/6 or Centos4/5 paravirtualized, it will not work. The VNC windows
doesn't pop up and I notice the guest shuts down. They work fine if
installed as fully virtualized guests as they should. Anything I need
to do to make paravirtualized work with these Distro's? Thanks to
everyone whos been helping this Xen beginner along.
On a side note, when I tried installing FreeBSD 6.2 fully virtualized,
it also didn't work. When I tried installing Debian, the install booted
fine and I was setting up the install when virtmanager complained about
something saying the install didn't work (even though it was running
fine) and closed/deleted the VM.
Marco Jorge
16 years, 9 months
Xen only showing 16GB of ram out of 28GB
by thewird
I installed FC6 and FC7 and the limit exists on both even though FC7
was supposed to be using a 64bit hypervisor which supports 32bit guests
(which isn't the case). After various linux installs (including CentOS)
and different configs (even replacing the hypervisor with its 64bit
counterpart) I wasn't able to get a system showing all 28GB of ram AND
work with 32bit guests.
Out of desperation I bought "Virtualization with Xen" on Amazon for
more insight. Although the book isn't too helpful since at least half
of it if not more, is advertising the commercial XenSource (why would I
buy an expensive Xen book if I wanted to use the newb commercial
software?) I was able to figure out how to install the latest version
of Xen 3.1 from source. I got it to boot perfectly and was expecting to
see all of my 28GB of ram when I ran top but to my dismay it only
showed 16GB once again...
Can someone please help me and tell me what am I doing wrong. Or am I
going about this the wrong way? Basically I want to see all of my 28GB
of ram and run 32bit guests. I read everywhere this can be done but it
never works. Thank you to anyone who can help me solve this. If money
is the problem, please say so and that can be arranged.
Marco Jorge
16 years, 9 months
No graphical console for HVM guests in F7?
by Felix Schwarz
Hi,
I recently migrated my Xen guests to a new host running F7 (64 bit), the old one
was FC6 (64 bit). After this migration, I do not have a graphical console for my
hvm guests when I double click a vm in virt-manager. This worked in FC6 and it
still works for pv guests.
The only exception is my 32 bit (hvm) Fedora 7 guest which I created at the new
host so it uses the new config system. This hvm guest is the only one which has
a graphical console.
I guess my problem is related to the Xen update from 3.0.3 -> 3.1 but I don't
know how to enable graphical consoles...
Thank you very much.
fs
16 years, 9 months
Unable to open connection to hypervisor 'qemu:///system'
by Justin Conover
virt-manager +kvm wont load up since the last rounds of F7 updates I think.
Unable to open connection to hypervisor URI 'qemu:///system':
<class 'libvirt.libvirtError'> virConnectOpenReadOnly() failed No such file
or directory
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 68, in
_connect_to_uri
conn = self.get_connection(uri, readOnly)
File "/usr/share/virt-manager/virtManager/engine.py", line 309, in
get_connection
conn = vmmConnection(self.get_config(), uri, readOnly)
File "/usr/share/virt-manager/virtManager/connection.py", line 74, in
__init__
self.vmm = libvirt.openReadOnly(openURI)
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 132, in
openReadOnly
if ret is None:raise libvirtError('virConnectOpenReadOnly() failed')
libvirtError: virConnectOpenReadOnly() failed No such file or directory
[root@echelon ~]# lsmod |grep kvm
kvm_amd 25813 1
kvm 75969 1 kvm_amd
This works:
[root@echelon kvm]# /usr/bin/qemu-kvm fedora7_1
16 years, 9 months
virsh and virt-install examples
by Thomas Antony
Hi,
I'm running F7 x86_64 with Xen 3.1 and need some advice.
I would be really happy if someone give me an example for adding a cdrom
(a iso file) to a (running) domain with virsh and install Windows Server
2003 on a lvm lg with virt-install.
thank you in advance,
Thomas Antony
16 years, 9 months
xen 3.1 network
by nooroon
Hello,
i'd like to understand more deeply xen networking.
My purpose is to modify the dscp ip field in guest's packet, to perform Qos,
thanks to iptables.
I'm using a FC7 with xen 3.1.
I've installed a windows guest, with virt-manager, and I have used the
default nat network option. Unfortunatelly, i couldn't use the bridge option
because no network card was proposed! but this isn't the subject...
I was quite surprised when i saw, in my xen-config.sxp : (network-script :
network-bridge). it should be network-nat, am I wrong?
the ifconfig command displays :
lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:731062 errors:0 dropped:0 overruns:0 frame:0
TX packets:731062 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:7695075004 (7.1 GiB) TX bytes:7695075004 (7.1 GiB)
tap0 Link encap:Ethernet HWaddr 82:E3:26:59:DC:BF
adr inet6: fe80::80e3:26ff:fe59:dcbf/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17783 errors:0 dropped:0 overruns:0 frame:0
TX packets:513 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:500
RX bytes:24458454 (23.3 MiB) TX bytes:181392 (177.1 KiB)
tmpbridge Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet adr:192.168.1.5 Bcast:192.168.1.255 Masque:255.255.255.0
adr inet6: fe80::200:ff:fe00:0/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:0 (0.0 b) TX bytes:9046 (8.8 KiB)
vif11.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:32
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
virbr0 Link encap:Ethernet HWaddr 82:E3:26:59:DC:BF
inet adr:192.168.122.1 Bcast:192.168.122.255 Masque:
255.255.255.0
adr inet6: fe80::200:ff:fe00:0/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21958 errors:0 dropped:0 overruns:0 frame:0
TX packets:1377 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:24771762 (23.6 MiB) TX bytes:304511 (297.3 KiB)
the "network-bridge status" displays :
============================================================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: peth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:08:02:f5:71:e6 brd ff:ff:ff:ff:ff:ff
3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether 82:e3:26:59:dc:bf brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
inet6 fe80::200:ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
4: tmpbridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/24 brd 192.168.1.255 scope global tmpbridge
inet6 fe80::200:ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
21: vif11.0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
qlen 32
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
22: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
500
link/ether 82:e3:26:59:dc:bf brd ff:ff:ff:ff:ff:ff
inet6 fe80::80e3:26ff:fe59:dcbf/64 scope link
valid_lft forever preferred_lft forever
it seems like the network-bridge scripts crashes, because the tmpbridge is
not renamed, and when I start the xend service or when I run network-bridge
start, the eth0 interface is disable!!
can anyone helps me debug this situation?
thanks
16 years, 9 months
RHEL 5 - Multiple Bridges with same Hardware Address
by Ubaidul Khan
I am writing this email in the hopes of getting some advice from Xen users.
My
main concern is performance and stability. Before I get any further, let me
explain the environment:
1. I am using redhat enterprise linux 5 with the xen kernel
(2.6.18-8.1.1.el5xen). This is on a Sun X4200 with two dual core AMD
processors, 16Gb of RAM, a Sun StoredgeTek 3320 attached to the
X4200, has a 4 port NIC.
2. eth0 is configured as the primary interface for the Domain-0 and is
attached to the xenbr0. I am using network-bridge model to provide
networking for the two guest domains. One of the domains is running NFS
server and needs to be configured with a private network address(on eth1).
3. So what I did is, I took eth1(on domain-0) and configured it on the
private
network. Then I created a script called
*custom-bridge*(this was mentioned in
(http://www.debian-administration.org/articles/470), with the following:
+-----------------------------------------------------------
| #!/bin/sh
| dir=$(dirname "$0")
| "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
| "$dir/network-bridge" "$@" vifnum=3 netdev=eth1 bridge=xenbr1
and modified xend-config.sxp in the following manner:
+-----------------------------------------------------------
| # The bridge is named xenbr0, by default. To rename the bridge,
use
| #
| # (network-script 'network-bridge bridge=<name>')
| #
| # It is possible to use the network-bridge script in more
complicated
| # scenarios, such as having two outgoing interfaces, with two
bridges, and
| # two fake interfaces per guest domain. To do things like this,
write
| # yourself a wrapper script, and call network-bridge from it, as
appropriate.
| #
| (network-script 'custom-bridge start')
The guest domain comes up fine and I am able to talk on the private network
from the guest domain and also from the private network to the guest
domain.
However, both of the bridges are configured with the same hardware address:
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
I think this is causing the following messages to show up on logs:
Jul 9 17:15:25 kernel: peth0: received packet with own address as source
address
Jul 9 17:19:38 kernel: peth0: received packet with own address as source
address
Jul 9 17:19:38 kernel: peth0: received packet with own address as source
address
Jul 9 17:19:42 kernel: peth0: received packet with own address as source
address
Jul 9 17:30:27 kernel: peth0: received packet with own address as source
address
Jul 9 17:30:27 kernel: peth0: received packet with own address as source
address
Jul 10 09:12:19 kernel: peth0: received packet with own address as source
address
Jul 10 10:06:04 kernel: peth0: received packet with own address as source
address
Jul 10 10:06:04 kernel: peth0: received packet with own address as source
address
Jul 10 10:06:05 kernel: peth0: received packet with own address as source
address
I am also seeing performance degradation. Any advice/suggestion is greatly
appreciated.
_________________________________________________________________
http://liveearth.msn.com
16 years, 9 months
