How is network bridging for Xen handled in F7?
by Christian Reiter
Hi!
Can anybody tell me where i can find docs about handling network bridges for xen domUs in Fedora 7?
Something changed since FC6, so i cannot figure out how to create simple bridges without dhcp for my xen domUs.
All what i want is:
xenbrINTERNET should bridge to eth1
xenbrLAN should bridge to eth0
eth0 and eth1 of my dom0 should also have an IP Address.
I do not want routing or nat for my domUs.
Thanks!
regards,
christian
15 years, 7 months
Guest VM dropping connection.
by Ubaidul Khan
I am running RHEL5 Guest and Host. The guest OS is dropping network
connections occasionally(I noticed my ssh session suddenly terminated). The
guest is configured with private network interface and a public network
interface. Following are the bridge/network settings for the host:
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif2.0
vif1.0
peth0
vif0.0
xenbr1 8000.fefffffffffe no vif2.1
peth1
vif0.3
xenbr1 is dedicated to provide the private network link for the guest os.
Following is the guest OS configuration:
# Automatically generated xen config file
name = "saleen_webvm0"
memory = "1000"
disk = [
'tap:aio:/vms/img/redhat/linux/es/5.0/x86_64/saleen_webvm0.img,xvda,w','phy:/dev/sdc,xvdb,w'
]
vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0','mac=00:16:3e:2f:9e:b1,
bridge=xenbr1',]
# vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0',]
vfb = ["type=vnc,vncunused=1"]
uuid = "122374dc-26a3-cb0d-99f8-3393e2481777"
bootloader="/usr/bin/pygrub"
vcpus=2
on_reboot = 'restart'
on_crash = 'restart'
Following is the output of ifconfig:
eth0 Link encap:Ethernet HWaddr 00:14:4F:40:D8:70
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255
Mask:255.255.255.0
inet6 addr: fe80::214:4fff:fe40:d870/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:79313 errors:0 dropped:0 overruns:0 frame:0
TX packets:1167 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6619719 (6.3 MiB) TX bytes:115448 (112.7 KiB)
eth1 Link encap:Ethernet HWaddr 00:14:4F:40:D8:71
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255
Mask:255.255.255.0
inet6 addr: fe80::214:4fff:fe40:d871/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:720 (720.0 b)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:105404 errors:0 dropped:0 overruns:0 frame:0
TX packets:13455 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9122426 (8.6 MiB) TX bytes:1997833 (1.9 MiB)
Base address:0x8c00 Memory:fa5e0000-fa600000
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FE
inet6 addr: fe80::fcff:ffff:feff:fffe/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:9239102 errors:0 dropped:0 overruns:0 frame:0
TX packets:5337342 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12420212276 (11.5 GiB) TX bytes:523849820 (499.5 MiB)
Base address:0x8800 Memory:fa5c0000-fa5e0000
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:2174 errors:0 dropped:0 overruns:0 frame:0
TX packets:80032 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:446031 (435.5 KiB) TX bytes:6941997 (6.6 MiB)
vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:10084 errors:0 dropped:0 overruns:0 frame:0
TX packets:89284 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:1186096 (1.1 MiB) TX bytes:7380350 (7.0 MiB)
vif2.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:5337343 errors:0 dropped:0 overruns:0 frame:0
TX packets:9239082 errors:0 dropped:20 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:403712612 (385.0 MiB) TX bytes:12383227754 (11.5 GiB)
Any help is greately appreciated.
_________________________________________________________________
http://liveearth.msn.com
15 years, 8 months
ID = VNC Port
by Juerg Ritter
Hello there!
I am wondering if there is a possibility to define that the VNC Port of
a virtual machine is always equal to the ID of the machine. That would
be very interesting for scripting, and easy to find out on which VNC
Display i have to search for a particular machine. Does anybody has an idea?
I would like to invoke something like:
vncviewer <dom0>:<ID>
to connect to this virtual machine.
thanks and regards,
Juerg
16 years
Fedora 7 kernels
by Jason Solan
I've had a lot of problems with Fedora 7 and XEN and I've read some
messages on this mailing list indicating the F7 kernel is more or less
broke with xen.
By problems I mean that 32 bit guests on 64 bit dom0 does not work at
all for me. Neither paravirtualized (as was a main feature of xen 3.1)
or fully virtualized.
Combinations I've tried:
F7 x86_64 dom0 -> F7 x86 domU PV
F7 x86_64 dom0 -> F7 x86 domU HVM
RHEL 5 x86_64 dom0 -> F7 x86 domU HVM
RHEL 5.1 Beta x86_64 dom0 -> F7 x86 domU PV
RHEL 5.1 Beta x86_64 dom0 -> F7 x86 domU HVM
RHEL 5 x86 dom0 -> F7 x86 domU PV -- Only one that works (32 on 32 PV)
I had read a while ago (June?) that a kernel update would be coming soon
to fix the 32 on 64 PV issue, however I've ran in several new kernels
and none seem to fix the issue.
https://www.redhat.com/archives/fedora-xen/2007-June/msg00031.html
I've also repeatedly tried to run a 32 bit HVM fedora 7 guest on 64 bit
machines and had that fail similar to this:
http://www.redhat.com/archives/fedora-xen/2007-June/msg00094.html
Is there any more work planned for Fedora 7 and xen, or should I just
wait until F8? Or am I just doing something wrong and the problems I'm
having should be working on the current builds?
IMPORTANT: This transmission is sent on behalf of Knouse Foods®
for business purposes. It is for the intended recipient only. If you are
not the intended recipient or a person responsible for delivering this
transmission to the intended recipient, you may not disclose, copy or
distribute this transmission or take any action in reliance on it.
If you received this transmission in error, please notify us immediately
by replying to this Email message, and please dispose of and delete
this transmission. Thank you.
16 years
Using virt
by Maximilian Freisinger
Hello, i have some question about virt-manager
1. Where is the script virt-manager uses for installation, and is it possible to modify?
2. Can i set kernelparameter for installation (i would need xfs)?
3. Is it possible to define single lvs as partitions for a new system?
THX DC
_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
16 years
Qemu goes bonkers - again!
by John Lagrue
I had an installation of WinXP that took a long time to install but
finally had running fairly well runing from a commandline call to
qemu-kvm (though I never have got the hang of how the network the
damned thing!)
But then, after a recent update, qemu-kvm would crash every time I
tried to run it. OK I thought, there's something new, so I tried to
create a new VM.
I still can't get anything useful to build with WinXP from
virt-manager, but did manage to get it to instal by running qemu-kvm
from the command line again. And it works fine. Right up to the moment
I install XP SP 2.
After that, all I get is this:
---------------------------------------------------------------
# qemu-kvm -localtime -no-acpi -m 512 CC3_1
Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal
error, but for better emulation accuracy either use a 2.6 host Linux kernel or
type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
unhandled vm exit: 0x3f60101
rax 00000000000000b5 rbx 00000000000000b5 rcx 0000000000000000 rdx
000000008053f118
rsi 0000000080551920 rdi 0000000000000000 rsp 00000000804d7000 rbp
000000008053f0a0
r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
0000000000000000
rip 000000008053f620 rflags 00000002
cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 0 avl 0)
ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0)
ldt 0000 (00000000/0000ffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
gdt 8003f000/3ff
idt 8003f400/7ff
cr0 8001003d cr2 0 cr3 a4a000 cr4 20 cr8 0 efer 0
Aborted
---------------------------------------------------------------
I've reinstalled this three times, and it happens every time. Does
this mean anything to anyone?
JDL
16 years
Creating and installing Centos under virt-manager
by John Lagrue
All working a treat: created the guest (fully virtualised - I have no
time for Xen), setup disk space in a 6Gb file, gave it a name, and
pointed the installation source to be the first of 6 .iso files for
Centos 5 installation
......then it asks for the second CDRom!
How the blazes is one supposed to tell it where to get the file?
I'm completely stuck! I thought this was supposed to work with .iso
files and I wouldn't have to burn 6 CDs. But what happens now?
JDL
16 years
Question: resize graphic console
by David Fischer (DHL US)
All,
The graphics console runs in 800x600 is there an option to change this?
thanks
--
David R. Fischer
Sr Systems Support Engineer
DHL Information Services (Americas)
8701 East Hartford Drive
Scottsdale, Arizona 85255 USA
Contact: +1.480.375.6428
Cell: +1.480.226.3779
16 years
Question: resize graphic console
by David R. Fischer
All,
The graphics console runs in 800x600 is there an option to change this?
It is kinda hard to understand how the default of 800x600 is picked up.
Is there a configuration file that sets the xen-vncfb setup?
thanks
David
16 years
Changing CDS
by Reed, Tameika N
Here is how I did when doing fully virtualized
1. First find out where the iso is mounted :
a. Xm block-list domain-name
This should return something similar to following:
Vdev BE Handle state evt-ch ring-ref BE-path
768 0 0 1 -1 -2
/local/domain/0/backend/vbd/8/768
5632 0 0 1 -1 -1
/local/domain/0/backend/vbd/8/5632
2. Now after finding that out do the following:
Xenstore-read /local/domain/0/backend/vbd/8/5632/params
This should return:
/root/rhel-5-server-i386-disc1.iso or wherever your isos are stored
3. Now can do the following to change which iso should be read:
Xenstore-read /local/domain/0/backend/vbd/8/5632/params
/root/rhel-5-server-i386-disc2.iso
16 years
