Xen Multiple Interface bridge creation fails

Hi,

I am using Xen 3.0.2 on SUSE SLES 10. I have created a script in 
/etc/xen/scripts called "network-mybridges" and use two lines to setup 
xenbr0 and xenbr1. When executed manually the script works fine and 
creates xenbr0 and xenbr1. I can then xm create -c <vmname>.
with absolutely no issues. It just won't work at boot time. It appears 
that the vif-bridge script is shutting down and deleting the devices 
(xenbr) at boot time instead of bringing them up. The script is 
configured into /etc/xen/xend-config.sxp.

Here is an excerpt from /var/log/messages:

   2357 May 31 16:57:04 zeus kernel: eth1: no IPv6 routers present
   2358 May 31 16:57:04 zeus logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_        PATH=backend/vif/1/0
   2359 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: add 
XENBUS_PATH=bac        kend/vbd/1/768
   2360 May 31 16:57:04 zeus logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_        PATH=backend/vif/1/1
   2361 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: add 
XENBUS_PATH=bac        kend/vbd/1/832
   2362 May 31 16:57:04 zeus kernel: NET: Registered protocol family 17
   2363 May 31 16:57:04 zeus ifup:     vif1.0
   2364 May 31 16:57:04 zeus ifup:               No configuration found 
for vif1        .0
   2365 May 31 16:57:04 zeus ifup:     vif1.1    2366 May 31 16:57:04 
zeus ifup:               No configuration found for vif1        .1
   2367 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: Writing 
backend/vbd        /1/768/node /dev/loop0 to xenstore.

Forcing a domain to run slowly

Is there an easy way to force a domain to slow down? I'm testing and
have just found that my Microsoft SBS2003 suddenly refuses to boot. I'm
trying to catch it to get it into safe mode but it goes too quick (I'm
out of the office and running over a slow link).

I start the domain paused, then open the vncviewer, then unpause it, so
I get to see the BIOS screen, but I can't see what happens next...

If I could slow it down to 1% (or even less) speed it might help a bit.

Any suggestions?

Thanks

James

Re: copy the running image, not working

great! I can write a script like :

# xm save dom-win2k somefile
# cp winsk.img win2k.img.bak
# cp somefile somefile.bak
# xm restore somefile

to run the backup every night.

Thanks a lot ! Mat.

cheers,
chen

Petersson, Mats wrote:

> 
>
>  
>
>>-----Original Message-----
>>From: xen-users-bounces <at> lists.xensource.com 
>>[mailto:xen-users-bounces <at> lists.xensource.com] On Behalf Of Xin Chen
>>Sent: 31 May 2007 13:01
>>To: xen-users
>>Subject: [Xen-users] copy the running image, not working
>>
>>Hi All,
>>
>>Domain 0 System: Fedora 6,  fc6xen. kernel 2.6.18, because 

Help: System crash when a large file is copied.

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

RE: [Xen-devel] Any known block device corruption problems in 3.1.0 upto release?

Oops... I meant to post this to xen-users.

I have gotten the server back up and running again by making the disk
accessible to another DomU and running a chkdsk on it that way. It found
a single corrupt index, repaired it, and everything is now fine. The
corruption was probably limited to a single block, and may have just
been caused by me shutting down the domain at exactly the wrong moment.

Can anyone comment on what write-back caching might be going on that
could cause these sorts of problems?

Thanks

James

Re: Setup WinXP with HVM and qemu image

Have you tried setting the cdrom to some device or file (ie disk = [ 
'file:/var/images/winxp.qcow,hda,w', 'file:/isoimage.iso,hdc:cdrom,r' ])?

Martin

Geert Janssens wrote:
> Hi,
>
> I am trying to accomplish the following:
> - The hardware is a recent HP workstation xw6400 with a dual core Xeon 
> processor. HVM is enabled in bios. 2Gb Ram available.
> - Dom0 is Centos 5, x86 (on xen 3.0.3 with redhat's modifications)
> - I would like to migrate a Qemu Windows XP installation to a xen hvm
>
> I figured this should not be too hard, because full virtualisation uses the 
> same (or allmost the same?) device model as qemu and under qemu, my Windows 
> XP installation is working fine.
>
> I have created a config file (see below), and started the guest domain with 
> xm create /etc/xen/WinXP.hvm
>
> xm then tells me that the domain was started succesfully, and xm list does 
> show it:
> [root <at> localhost ~]# xm list
> Name                                      ID Mem(MiB) VCPUs State   Time(s)
> Domain-0                                   0     1488     2 r-----    185.5
> WindowsXP                                  6      517     1 ------      0.0
>
> However, I can't find a way to connect to it via vnc. I tried
> vncviewer localhost:10
>
> But this returns immediatly with
> VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02
> Copyright (C) 2002-2005 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
>
> Thu May 31 22:53:15 2007
>  main:        unable to connect to host: Connection refused (111)
>
> What is happening here ?
>
> Below is my Guest domain's config. I have set the options to match the 
> original qemu config as close as possible.
> #  -*- mode: python; -*-
> #============================================================================
> # Python configuration setup for 'xm create'.
> # This script sets the parameters used when a domain is created using 'xm 
> create'.
> # You use a separate script for each domain you want to create, or
> # you can set the parameters for the domain on the xm command line.
> #============================================================================
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 512
> shadow_memory = 8
> name = "WindowsXP"
> vcpus=2
> #pae=0
> #acpi=0
> #apic=0
> vif = [ 'type=ioemu, mac=00:18:32:6c:00:ba, bridge=xenbr0' ]
> disk = [ 'file:/var/images/winxp.qcow,hda,w', ',hdc:cdrom,r' ]
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> sdl=0
> vnc=1
> vncdisplay=10
> vncconsole=0
> vncpasswd=''
> stdvga=1
> serial='pty'
> soundhw='sb16'
> usb=1
> usbdevice='tablet'
> keymap='be'
>
>
> Geert
>
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users
>   

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

Re: Setup WinXP with HVM and qemu image

...
> xm then tells me that the domain was started succesfully, and xm list does 
> show it:
> [root <at> localhost ~]# xm list
> Name                                      ID Mem(MiB) VCPUs State   Time(s)
> Domain-0                                   0     1488     2 r-----    185.5
> WindowsXP                                  6      517     1 ------      0.0
> 
> However, I can't find a way to connect to it via vnc. I tried
> vncviewer localhost:10
> 
> But this returns immediatly with
> VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02
> Copyright (C) 2002-2005 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
> 
> Thu May 31 22:53:15 2007
>  main:        unable to connect to host: Connection refused (111)
> 
> What is happening here ?

You can check what ports are opened with command:

# netstat -lnp -A inet

> [root <at> localhost ~]# xm list
> Name                                      ID Mem(MiB) VCPUs State   Time(s)
> Domain-0                                   0     1488     2 r-----    185.5
> WindowsXP                                  6      517     1 ------      0.0

Also, It seems strange to me that WindowsXP Time = 0.0.
If the domain were running that field AFIAK would not be equal to 0.0

--

-- 
WBR, i.m.chubin

Re: Setup WinXP with HVM and qemu image

Another idea.

In this line:
> disk = [ 'file:/var/images/winxp.qcow,hda,w', ',hdc:cdrom,r' ]

you specify winxp.qcow file to use as disk for Xen domain.

AFAIK you must use raw images, but not qcow.

To convert qcow image to raw format
you can use the command:

qemu-img convert winxp.qcow -O raw winxp.img

After that you can check that winxp.img is correct raw image
with fdisk command (fdisk should show partition table on the image).

fdisk -l winxp.img

--

-- 
WBR, i.m.chubin

Re: cannot use vncviewer and VMM graphics console to access HVM guest on RHES 5

Use netstat to verify the port VNC is listening on, or change 
vncunused=1 to vncunused=0 and set vncdisplay=somenumber.  vncunused=1 
will cause it to pick an unused display, which might not be equal to the 
guest id.

Martin

Glen Deem wrote:
> Hi all,
>
> I've created an HVM guest under RHES 5 (Xen 3.0.3) using "xm create"
> but I cannot access it with vncviewer.
>
> The Virtual Machine Manager also informs about graphics console 
> unavailability.
>
> What am I doing wrong, please?
>
> I do
>> vncviewer 123.456.789.123:4,
> where 4 is the guest id.
>
> This is the xm config file is:
>
> name = "hvmGuest"
> builder = "hvm"
> memory = "500"
> disk = [ 'file:/var/lib/red-hat.img,hda,w', ]
> vif = [ 'type=ioemu, mac=00:16:3e:34:3b:ba, bridge=xenbr0', ]
> device_model = "/usr/lib/xen/bin/qemu-dm"
> kernel = "/usr/lib/xen/boot/hvmloader"
> vnc=1
> vncunused=1
> apic=1
> acpi=1
> pae=1
> vcpus=1
> serial = "pty"
> on_reboot   = 'restart'
> on_crash    = 'restart'
>
> Thanks a lot in advance.
>
> Glen from Ottawa, Canada
>
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

RE: low network performance

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users