[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card error



Hello Walter,

good news - congratulations :)

Do you have .deb packages for xen 4.2 unstable and the xen-kernel you have used?

Thank you for your short info.

regards,
Mark


Am 25.07.2011 00:21, schrieb Walter Robert Ditzler:
hi list members,

i had several problems with my new xen installations, 4.2 unstable with
2.6.39-3 and hvm guests. I can finally say that almost all problems have
been gone :-) to  be honest I believe the kernels 2.6.39.1/2 and 3 were the
problem.

this weekend I used the mainline 3.0.0 kernel with an actual version of xen
4.2 unstable, and here we go:

- booting of squeeze guests, ok (before hang on grub)
- booting of win 7 x64 guests, ok
- booting of win 2008r2 x64 guests, ok

the only little problem which has left is on squeeze guests.

the squeeze guest comes up until grub. but then it takes around 2 minutes
until the squeeze guest installation continues to start up. that would be
really nice get to be solved in the near future.

thanks walter







-----Original Message-----
From: Walter Robert Ditzler [mailto:ditwal001@xxxxxxxxx]
Sent: Mittwoch, 20. Juli 2011 14:09
To: 'Stefano Stabellini'
Cc: konrad.wilk@xxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx;
xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card
error
Importance: High

stefano,

i found the problem, if it is really a one! I will explain it step by step
what solved my problem which works for both, win7 and debian squeeze
guest's:

network card / network
**********************
the guest network works brilliant only with that configuration:

auto brX
iface brX inet static
         address         10.41.10.42
         netmask         255.255.255.0
         network         10.41.10.0
         broadcast       10.41.10.255
         gateway         10.41.10.1
         bridge_ports    eth0
         bridge_stp      on
         bridge_maxwait  0

vif             = [ 'bridge=brX,mac=xx:xx:xx:xx:xx:xx' ]


strange is that I now have to configure a bridge interface. with older xen
version it was enough to setup "bridge=eth0". now I had to setup
"bridge=brX"!


disk controller
***************
for a windows 7 x64 guest system I got it running with:
disk            = [
'phy:/dev/vgmain/lv_server01,hda,w','file:/var/xen/win7.iso,hdc:cdrom,r' ]

for a debian squeeze guest system I needed to change it into:
disk            = [
'phy:/dev/vgmain/lv_server01,sda,w','file:/var/xen/debian-6.0.1a-amd64-netin
st.iso,hdc:cdrom,r' ]


even here is strange that debian squeeze guest's now see the qemu disk as a
"SDA". squeeze used to see qemu disk in older xen versions (<  4.2) as "HDA"
and that definitely doesn't work anymore.

I found that out having a deeper look at the debian installer log.


guy's, thank you very much for your help, had become a lot of new input's. I
hope I could give some useful feedback back to you too.

finally I only would like to know, if this SDA-behavior is now a new
behavior of xen 4.2 ++?

thanks a lot, walter



*** original guest config file ***
name            = 'server01'
kernel          = 'hvmloader'
builder         = 'hvm'
device_model    = 'qemu-dm'
maxmem          = 1024
memory          = 1024
vcpus           = 1
acpi            = 1
apic            = 1

vif             = [ 'bridge=eth0,mac=00:16:3e:1a:b3:4b' ]
#vfb            = [ 'type=vnc,vnclisten=0.0.0.0,vncunused=0,vncdisplay=1' ]

disk            = [
'phy:/dev/vgmain/lv_server01,hda,w','file:/var/xen/debian-6.0.1a-amd64-netin
st.iso,hdc:cdrom,r' ]

boot            = 'dc'
usbdevice       = 'tablet'

sdl             = 0

stdvga          = 1
serial          = 'pty'

on_poweroff     = 'destroy'
on_reboot       = 'restart'
on_crash        = 'restart'

vnc             = 1
vnclisten       = '0.0.0.0'
vncviewer       = 1
***




-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@xxxxxxxxxxxxx]
Sent: Mittwoch, 20. Juli 2011 13:40
To: Walter Robert Ditzler
Cc: Stefano Stabellini; konrad.wilk@xxxxxxxxxx;
xen-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card
error

On Tue, 19 Jul 2011, Walter Robert Ditzler wrote:
hi stefano,
hi konrad,

thanks for replying :-) i followed your suggestions and changed the
guest config file. I have now the following test szenario:

server01>  should be a debian squeeze 6.0.1a amd64 netinst
installation
server02>  is a successfully installed windows 7 x64 installation

bellow I paste the both config files. as you can see from the screen
shots:
server01 installation
*********************
sh11: server01_debian-installer-1.JPG
sh12: server01_debian-installer-2.JPG
sh13: server01_debian-installer-3.JPG

the debian installation has some difficulties to find a harddisk.
strange is, that the networkcard was found straight away and I became
a dhcp lease from my infrastructure.

server02 installation
*********************
sh21: server02_xen_win7.JPG

the windows has been successfully installed onto my xen guest, but!!!!!


Q U E S T I O N S
*****************
- why do I see my server HP DL320G5 network card and disk controller?
- I thought, HVM means fully virtualized?! I expected to see something
like qemu/xen harddrive and qemu/xen network card!?
- Is here my xen really doing HVM
- how can I do HVM, I need my guests to be transferred to any
different hw boxes without need to deal with guest disk and network
card
drivers?

What exactly are the network card and disk controller that you are seeing in
your guests?



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


--
IT-Infrastrukturen.ORG

ms@xxxxxxxxxxxxxxxxxxxxxx
http://www.it-infrastrukturen.org

+++ Free infrastructure software for all. +++


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.