Xen devel - Jul 2011 - xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card error

hi folks,

after long trying i need some help from the big world :-)

question
********
when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors
like:

1) after click install on debian 6.0.2 installer
[0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632
[0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19
xenbus_dev_probe on device/vbd/5632)

2) network
no dhcp server found, ask me to setup ip manually, cause no network card
found

3) disk
stops at the disk detection, no appropriate driver found

also no hw stuff found while trying to install windows 7 x64.

I have a 4.0.1 on squeeze running and productive, I am not a newbe, but at
the end with my latin.

can anyone help me out here?

below my system info''s!
attached some more system info like:

/var/log/xen
- xl-server02.log
- qemu-dm-server02.log
- xen-hotplug.log

console
- dmesg
- lspci
- xl dmesg

thanks a lot, walter


guest config
************

***
name            = ''server02''
kernel          = ''/usr/lib64/xen/boot/hvmloader''
builder         = ''hvm''
device_model    = ''/usr/lib64/xen/bin/qemu-dm''
maxmem          = 1024
memory          = 1024
vcpus           = 1
acpi            = 0
#apic            = 1

vif             = [''bridge=eth0'']
disk           
[''phy:/dev/vgmain/lv_server02,xvda,w'',''phy:/var/xen/firmware-6.0.2.1-amd64-n
etinst.iso,hdc:cdrom,r'']

boot            = ''cd''
usbdevice       = ''tablet''

extra           = ''swiotlb=force iommu=soft''

vnc             = 1
#vncunused      = 0
vnclisten       = ''0.0.0.0''
#vncdisplay     = 2
#vncconsole     = 1
#vncpasswd      = ''123456''
vncviewer       = 1

#sdl             = 0

stdvga          = 1
serial          = ''pty''
#ne2000          = "1"

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



***
root@srv-ldeb-xen001:/etc/xen# xl info
host                   : srv-ldeb-xen001
release                : 2.6.39.3
version                : #1 SMP Wed Jul 13 15:15:50 CEST 2011
machine                : x86_64
nr_cpus                : 1
nr_nodes               : 1
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 2128
hw_caps                :
bfebfbff:20000800:00000000:00000940:0000e3bd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 8190
free_memory            : 6029
free_cpus              : 0
xen_major              : 4
xen_minor              : 2
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Thu Jul 14 13:24:19 2011 +0100 23695:fbb448cf5cba
xen_commandline        : dummy dom0_mem=1024M
cc_compiler            : gcc version 4.4.5 (Debian 4.4.5-8)
cc_compile_by          : root
cc_compile_domain      : local.ch
cc_compile_date        : Sun Jul 17 00:21:53 CEST 2011
xend_config_format     : 4
root@srv-ldeb-xen001:/etc/xen#
***



***
xentop - 19:31:59   Xen 4.2-unstable
2 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 8386580k total, 2212596k used, 6173984k free    CPUs: 1 @ 2128MHz
      NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%)
VCPUS NETS NETTX(k) NETRX(k) VBDS   VBD_OO   VBD_RD   VBD_WR  VBD_RSECT
VBD_WSECT SSID
  Domain-0 -----r        804   10.1    1048576   12.5   no limit       n/a
1    0        0        0    0        0        0        0          0
0    0
  server02 --b---          7    1.0    1048476   12.5    1049600      12.5
1    1        0        0    0        0        0        0          0
0    0
***







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

On Sun, 17 Jul 2011, Walter Robert Ditzler wrote:
> hi folks,
> 
> after long trying i need some help from the big world :-)
> 
> question
> ********
> when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors
> like:
> 
> 1) after click install on debian 6.0.2 installer
> [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632
> [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19
> xenbus_dev_probe on device/vbd/5632)
> 
> 2) network
> no dhcp server found, ask me to setup ip manually, cause no network card
> found
> 
> 3) disk
> stops at the disk detection, no appropriate driver found
> 
> also no hw stuff found while trying to install windows 7 x64.
> 
> I have a 4.0.1 on squeeze running and productive, I am not a newbe, but at
> the end with my latin.
> 
> can anyone help me out here?
> 
> below my system info''s!
> attached some more system info like:
> 
> /var/log/xen
> - xl-server02.log
> - qemu-dm-server02.log
> - xen-hotplug.log
> 
> console
> - dmesg
> - lspci
> - xl dmesg
> 
> thanks a lot, walter
> 
> 
> guest config
> ************
> 
> ***
> name            = ''server02''
> kernel          = ''/usr/lib64/xen/boot/hvmloader''
> builder         = ''hvm''
> device_model    = ''/usr/lib64/xen/bin/qemu-dm''
> maxmem          = 1024
> memory          = 1024
> vcpus           = 1
> acpi            = 0
> #apic            = 1
> 
> vif             = [''bridge=eth0'']
> disk            >
[''phy:/dev/vgmain/lv_server02,xvda,w'',''phy:/var/xen/firmware-6.0.2.1-amd64-n
> etinst.iso,hdc:cdrom,r'']
Considering that this is an hvm guest and that you only have one disk,
it should be hda rather than xvda.
Also it is probably not a good idea to disable acpi.

> boot            = ''cd''
> usbdevice       = ''tablet''
> 
> extra           = ''swiotlb=force iommu=soft''
this is an hvm guest so extra is not going to do much, you need to pass
these parameters directly to the guest kernel from grub if you want them.



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

On Mon, Jul 18, 2011 at 12:47:49PM +0100, Stefano Stabellini
wrote:
> On Sun, 17 Jul 2011, Walter Robert Ditzler wrote:
> > hi folks,
> > 
> > after long trying i need some help from the big world :-)
> > 
> > question
> > ********
> > when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get
errors
> > like:
> > 
> > 1) after click install on debian 6.0.2 installer
> > [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632
> > [0.642911] vbd vbd-5632: failed to write error node for
device/vbd/5632 (19
> > xenbus_dev_probe on device/vbd/5632)
> > 
> > 2) network
> > no dhcp server found, ask me to setup ip manually, cause no network
card
> > found
> > 
> > 3) disk
> > stops at the disk detection, no appropriate driver found
> > 
> > also no hw stuff found while trying to install windows 7 x64.
> > 
> > I have a 4.0.1 on squeeze running and productive, I am not a newbe,
but at
> > the end with my latin.
> > 
> > can anyone help me out here?
> > 
> > below my system info''s!
> > attached some more system info like:
> > 
> > /var/log/xen
> > - xl-server02.log
> > - qemu-dm-server02.log
> > - xen-hotplug.log
> > 
> > console
> > - dmesg
> > - lspci
> > - xl dmesg
> > 
> > thanks a lot, walter
> > 
> > 
> > guest config
> > ************
> > 
> > ***
> > name            = ''server02''
> > kernel          = ''/usr/lib64/xen/boot/hvmloader''
> > builder         = ''hvm''
> > device_model    = ''/usr/lib64/xen/bin/qemu-dm''
> > maxmem          = 1024
> > memory          = 1024
> > vcpus           = 1
> > acpi            = 0
> > #apic            = 1
> > 
> > vif             = [''bridge=eth0'']
> > disk            > >
[''phy:/dev/vgmain/lv_server02,xvda,w'',''phy:/var/xen/firmware-6.0.2.1-amd64-n
> > etinst.iso,hdc:cdrom,r'']
> 
> Considering that this is an hvm guest and that you only have one disk,
> it should be hda rather than xvda.
> Also it is probably not a good idea to disable acpi.
> 
> 
> > boot            = ''cd''
> > usbdevice       = ''tablet''
> > 
> > extra           = ''swiotlb=force iommu=soft''
> 
> this is an hvm guest so extra is not going to do much, you need to pass
> these parameters directly to the guest kernel from grub if you want them.
And not sure if you want to do that. You will enable bounce buffer
for _ANY_ DMA transaction. Get rid of that ''swiotlb=force''.
You don''t
need iommu=soft either as your are running in HVM mode.


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

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?




many thanks, walter




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

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

boot            = ''cd''
usbdevice       = ''tablet''

sdl             = 0

stdvga          = 1
serial          = ''pty''
ne2000          = 1

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

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


server02
********
name            = ''server02''
kernel          = ''hvmloader''
builder         = ''hvm''
device_model    = ''qemu-dm''
maxmem          = 1024
memory          = 1024
vcpus           = 1
acpi            = 1
apic            = 1

vif             = [ ''bridge=eth0'' ]

disk            = [
''phy:/dev/vgmain/lv_server02,hda,w'',''file:/var/xen/win7.iso,hdc:cdrom,r''
]

boot            = ''cd''
usbdevice       = ''tablet''

sdl             = 0

stdvga          = 1
serial          = ''pty''

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

vnc             = 1
#vncunused      = 0
vnclisten       = ''0.0.0.0''
#vncdisplay     = 2
#vncconsole     = 1
#vncpasswd      = ''123456''
vncviewer       = 1

ne2000          = 1
***



-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com] 
Sent: Montag, 18. Juli 2011 13:48
To: Walter Robert Ditzler
Cc: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
Subject: Re: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card
error

On Sun, 17 Jul 2011, Walter Robert Ditzler wrote:
> hi folks,
> 
> after long trying i need some help from the big world :-)
> 
> question
> ********
> when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get 
> errors
> like:
> 
> 1) after click install on debian 6.0.2 installer [0.642450] vbd 
> vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd 
> vbd-5632: failed to write error node for device/vbd/5632 (19 
> xenbus_dev_probe on device/vbd/5632)
> 
> 2) network
> no dhcp server found, ask me to setup ip manually, cause no network 
> card found
> 
> 3) disk
> stops at the disk detection, no appropriate driver found
> 
> also no hw stuff found while trying to install windows 7 x64.
> 
> I have a 4.0.1 on squeeze running and productive, I am not a newbe, 
> but at the end with my latin.
> 
> can anyone help me out here?
> 
> below my system info''s!
> attached some more system info like:
> 
> /var/log/xen
> - xl-server02.log
> - qemu-dm-server02.log
> - xen-hotplug.log
> 
> console
> - dmesg
> - lspci
> - xl dmesg
> 
> thanks a lot, walter
> 
> 
> guest config
> ************
> 
> ***
> name            = ''server02''
> kernel          = ''/usr/lib64/xen/boot/hvmloader''
> builder         = ''hvm''
> device_model    = ''/usr/lib64/xen/bin/qemu-dm''
> maxmem          = 1024
> memory          = 1024
> vcpus           = 1
> acpi            = 0
> #apic            = 1
> 
> vif             = [''bridge=eth0'']
> disk            >
[''phy:/dev/vgmain/lv_server02,xvda,w'',''phy:/var/xen/firmware-6.0.2.1-a
> md64-n
> etinst.iso,hdc:cdrom,r'']
Considering that this is an hvm guest and that you only have one disk, it
should be hda rather than xvda.
Also it is probably not a good idea to disable acpi.

> boot            = ''cd''
> usbdevice       = ''tablet''
> 
> extra           = ''swiotlb=force iommu=soft''
this is an hvm guest so extra is not going to do much, you need to pass
these parameters directly to the guest kernel from grub if you want them.










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

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@lists.xensource.com
http://lists.xensource.com/xen-devel

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@eu.citrix.com] 
Sent: Mittwoch, 20. Juli 2011 13:40
To: Walter Robert Ditzler
Cc: Stefano Stabellini; konrad.wilk@oracle.com;
xen-devel@lists.xensource.com; xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-devel

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@gmail.com]
> Sent: Mittwoch, 20. Juli 2011 14:09
> To: ''Stefano Stabellini''
> Cc: konrad.wilk@oracle.com; xen-devel@lists.xensource.com;
> xen-users@lists.xensource.com
> 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@eu.citrix.com]
> Sent: Mittwoch, 20. Juli 2011 13:40
> To: Walter Robert Ditzler
> Cc: Stefano Stabellini; konrad.wilk@oracle.com;
> xen-devel@lists.xensource.com; xen-users@lists.xensource.com
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>    

-- 
IT-Infrastrukturen.ORG

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

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


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

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@gmail.com] 
Sent: Mittwoch, 20. Juli 2011 14:09
To: ''Stefano Stabellini''
Cc: konrad.wilk@oracle.com; xen-devel@lists.xensource.com;
xen-users@lists.xensource.com
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@eu.citrix.com]
Sent: Mittwoch, 20. Juli 2011 13:40
To: Walter Robert Ditzler
Cc: Stefano Stabellini; konrad.wilk@oracle.com;
xen-devel@lists.xensource.com; xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-devel

nope, but have all documented in 2 txt file, 1 is the kernel config and the
other a complete install after having a running virgin squeeze box.
checkinstall made problems.

thanks walter

-----Original Message-----
From: Mark Schneider [mailto:ms@it-infrastrukturen.org] 
Sent: Sonntag, 24. Juli 2011 23:33
To: Walter Robert Ditzler; xen-devel@lists.xensource.com
Subject: 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@gmail.com]
> Sent: Mittwoch, 20. Juli 2011 14:09
> To: ''Stefano Stabellini''
> Cc: konrad.wilk@oracle.com; xen-devel@lists.xensource.com; 
> xen-users@lists.xensource.com
> 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@eu.citrix.com]
> Sent: Mittwoch, 20. Juli 2011 13:40
> To: Walter Robert Ditzler
> Cc: Stefano Stabellini; konrad.wilk@oracle.com; 
> xen-devel@lists.xensource.com; xen-users@lists.xensource.com
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>    

--
IT-Infrastrukturen.ORG

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

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



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

On Sun, 24 Jul 2011, Walter Robert Ditzler wrote:
> 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.
Can you please add debug and loglevel=9 to the guest kernel command line
options and then post the output of the guest booting?
It might help to setup the guest to use the emulated serial.
Also it would be helpful if you could post the output of xenstore-ls run
on the host.

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

hi stefanao,

i have you added loglevel=9 in grub

***
### BEGIN /etc/grub.d/08_xen ###
menuentry "Xen 4.2 Unstable / Debian Squeeze kernel 3.0.0" {
        insmod ext2
        insmod multiboot2
        insmod lvm
        insmod part_msdos
        insmod raid
        insmod mdraid
        set root=''(md/1)''
        search --no-floppy --fs-uuid --set
8809ff98-9ce8-472a-9ae9-74b821fe5285
        echo ''Loading multiboot kernel ...''
        multiboot (md/1)/boot/xen.gz placeholder dom0_mem=1024M loglevel=9
        echo ''Loading initial kernel ...''
        module (md/1)/boot/vmlinuz-3.0.0 placeholder
root=UUID=8809ff98-9ce8-472a-9ae9-74b821fe5285 ro quiet console=tty0
nomodeset
        echo ''Loading initial ramdisk ...''
        module (md/1)/boot/initrd.img-3.0.0
}
### END /etc/grub.d/08_xen ###
***

and several log files attached to this email.

thanks a lot for your help,

walter.





-----Original Message-----
From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com] 
Sent: Montag, 25. Juli 2011 12:43
To: Walter Robert Ditzler
Cc: Stefano Stabellini; konrad.wilk@oracle.com;
xen-devel@lists.xensource.com; xen-users@lists.xensource.com
Subject: RE: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card
error

On Sun, 24 Jul 2011, Walter Robert Ditzler wrote:
> 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.
Can you please add debug and loglevel=9 to the guest kernel command line
options and then post the output of the guest booting?
It might help to setup the guest to use the emulated serial.
Also it would be helpful if you could post the output of xenstore-ls run on
the host.










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

On Mon, 25 Jul 2011, Walter Robert Ditzler wrote:
> hi stefanao,
> 
> i have you added loglevel=9 in grub
> 
> ***
> ### BEGIN /etc/grub.d/08_xen ###
> menuentry "Xen 4.2 Unstable / Debian Squeeze kernel 3.0.0" {
>         insmod ext2
>         insmod multiboot2
>         insmod lvm
>         insmod part_msdos
>         insmod raid
>         insmod mdraid
>         set root=''(md/1)''
>         search --no-floppy --fs-uuid --set
> 8809ff98-9ce8-472a-9ae9-74b821fe5285
>         echo ''Loading multiboot kernel ...''
>         multiboot (md/1)/boot/xen.gz placeholder dom0_mem=1024M loglevel=9
>         echo ''Loading initial kernel ...''
>         module (md/1)/boot/vmlinuz-3.0.0 placeholder
> root=UUID=8809ff98-9ce8-472a-9ae9-74b821fe5285 ro quiet console=tty0
> nomodeset
>         echo ''Loading initial ramdisk ...''
>         module (md/1)/boot/initrd.img-3.0.0
> }
> ### END /etc/grub.d/08_xen ###
> ***
> 
> and several log files attached to this email.
I need the output of the guest kernel stuck during boot in order to
understand the problem. It shouldn''t be difficult to get if you enable
logging over the serial in the guest kernel.

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

here we go:

1) compile a kernel
*******************
i did that on a separate host, kernel config file attached (config-3.0.0)

source:
- http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.tar.bz2

important: don''t apply git4 patch, doesn''t work yet with xen,
xen host
doesn''t boot anymore.


xen host
********
2xhd250gb
2xhd2tb
16gb ram
hp dl 320g5

partitions raid 1
*****************
md0 > 12gb > swap
md1 > 238gb > ext4 /
md2 > 2tb > lvm2

lvm2
****
lv group > vgmain
lv device > lv_server01 > 100gb


2) xen host configuration
*************************

debian squeeze install 6.0.2.1, without preselected package, plain.

http://cdimage.debian.org/debian-cd/6.0.2.1/amd64/iso-cd/debian-6.0.2.1-amd6
4-netinst.iso

aptitude install lsof mc ssh console-data git-core mercurial locales udev
initramfs-tools

rm -r /etc/resolv.conf
touch /etc/resolv.conf
nano /etc/resolv.conf

***
domain domain.net
search *
nameserver 212.40.0.10
nameserver 212.40.5.50
***


rm -r /etc/kernel-img.conf
touch /etc/kernel-img.conf
nano /etc/kernel-img.conf

***
do_symlinks	= yes
relative_links	= yes
do_bootloader	= no
do_bootfloppy	= no
do_initrd	= yes
link_in_boot	= no
***


aptitude update

dpkg-reconfigure locales
dpkg-reconfigure tzdata
dpkg-reconfigure console-data

aptitude update
aptitude safe-upgrade
apt-get clean
aptitude clean

rm -r /etc/inittab
touch /etc/inittab
nano /etc/inittab

***
id:2:initdefault:
si::sysinit:/etc/init.d/rcS
~~:S:wait:/sbin/sulogin

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6

z6:6:respawn:/sbin/sulogin
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop

1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
***


rm -r /etc/ssh/sshd_config
touch /etc/ssh/sshd_config
nano /etc/ssh/sshd_config

***
Port				22
#ListenAddress			::
#ListenAddress			0.0.0.0
Protocol			2
HostKey				/etc/ssh/ssh_host_rsa_key
HostKey				/etc/ssh/ssh_host_dsa_key
UsePrivilegeSeparation		yes
KeyRegenerationInterval		3600
ServerKeyBits			768
SyslogFacility			AUTH
LogLevel			INFO
LoginGraceTime			120
PermitRootLogin			no
StrictModes			yes
RSAAuthentication		yes
PubkeyAuthentication		yes
#AuthorizedKeysFile		%h/.ssh/authorized_keys
IgnoreRhosts			yes
RhostsRSAAuthentication		no
HostbasedAuthentication		no
#IgnoreUserKnownHosts		yes
PermitEmptyPasswords		no
ChallengeResponseAuthentication	no
#PasswordAuthentication		yes
#KerberosAuthentication		no
#KerberosGetAFSToken		no
#KerberosOrLocalPasswd		yes
#KerberosTicketCleanup		yes
#GSSAPIAuthentication		no
#GSSAPICleanupCredentials	yes
X11Forwarding			yes
X11DisplayOffset		10
PrintMotd			no
PrintLastLog			yes
TCPKeepAlive			yes
#UseLogin			no
#MaxStartups			10:30:60
#Banner				/etc/issue.net
AcceptEnv			LANG LC_*
Subsystem sftp			/usr/lib/openssh/sftp-server
UsePAM				yes
***


# xen install
aptitude install gcc make uuid-dev libcurl4-openssl-dev flex gettext
libncurses5-dev bin86 bcc iasl python-dev python texinfo texi2html
pciutils-dev bison bzip2 checkinstall autoconf debhelper debconf-utils
docbook-xml docbook-xsl dpatch xsltproc bridge-utils

cd /usr/src

hg clone http://xenbits.xensource.com/xen-unstable.hg xen-unstable

cd /usr/src/xen-unstable

make clean
make xen
make tools
make stubdom

make install-xen
make install-tools PYTHON_PREFIX_ARGmake install-stubdom


rm -r /etc/network/interfaces
touch /etc/network/interfaces
nano /etc/network/interfaces

***
auto lo
iface lo inet loopback

auto br0
iface br0 inet static
        address         10.10.10.21
        netmask         255.255.255.0
        network         10.10.10.0
        broadcast       10.10.10.255
        gateway         10.10.10.1
        bridge_ports    eth0
        bridge_stp      on
        bridge_maxwait  0

auto eth1
iface eth1 inet static
        address         10.255.255.1
        netmask         255.255.255.0
        network         10.255.255.0
        broadcast       10.255.255.255
***


rm -r /etc/sysctl.conf
touch /etc/sysctl.conf
nano /etc/sysctl.conf

***
kernel.domainname                       = local.net
#kernel.printk                          = 3 4 1 3
#net.ipv4.conf.default.rp_filter        = 1
#net.ipv4.conf.all.rp_filter            = 1
#net.ipv4.tcp_syncookies                = 1
net.ipv4.ip_forward                     = 1
net.ipv6.conf.all.forwarding            = 1
#net.ipv4.conf.all.accept_redirects     = 0
#net.ipv6.conf.all.accept_redirects     = 0
#net.ipv4.conf.all.send_redirects       = 0
#net.ipv4.conf.all.accept_source_route  = 0
#net.ipv6.conf.all.accept_source_route  = 0
#net.ipv4.conf.all.log_martians         = 1
***


rm -r /etc/xen/xend-config.sxp
touch /etc/xen/xend-config.sxp
nano /etc/xen/xend-config.sxp

***
# -*- sh -*-
#(logfile /var/log/xen/xend.log)
#(loglevel DEBUG)
#(xsm_module_name dummy)
#(xen-api-server ((unix)))
#(xend-http-server no)
#(xend-unix-server no)
#(xend-tcp-xmlrpc-server no)
#(xend-unix-xmlrpc-server yes)
(xend-relocation-server yes)
#(xend-relocation-ssl-server no)
#(xend-udev-event-server no)
#(xend-unix-path /var/lib/xend/xend-socket)
#(xend-tcp-xmlrpc-server-address ''localhost'')
#(xend-tcp-xmlrpc-server-port 8006)
#(xend-tcp-xmlrpc-server-ssl-key-file  xmlrpc.key)
#(xend-tcp-xmlrpc-server-ssl-cert-file xmlrpc.crt)
#(xend-port 8000)
(xend-relocation-port 8002)
#(xend-relocation-ssl-port 8003)
# xend-relocation-ssl-server is set.
#(xend-relocation-server-ssl-key-file   xmlrpc.key)
#(xend-relocation-server-ssl-cert-file  xmlrpc.crt)
#(xend-relocation-ssl no)
#(xend-address '''')
#(xend-address localhost)
(xend-relocation-address '''')
#(xend-relocation-hosts-allow '''')
(xend-relocation-hosts-allow ''^localhost$
^localhost\\.localdomain$'')
#(console-limit 1024)
(network-script ''network-bridge antispoof=yes'')
(vif-script vif-bridge)
#(vif-script vif-route)
#(vif-script vif-nat)
(dom0-min-mem 256)
(enable-dom0-ballooning yes)
(total_available_memory 0)
(dom0-cpus 0)
#(enable-dump no)
#(external-migration-tool '''')
(vnc-listen ''0.0.0.0'')
(vncpasswd '''')
#(vnc-tls 1)
#(vnc-x509-cert-dir vnc)
#(vnc-x509-verify 1)
(keymap ''de-ch'')
#(resource-label-change-script '''')
#(qemu-dm-logrotate-count 10)
#(xend-domains-path /var/lib/xend/domains)
#(device-create-timeout 100)
#(pscsi-device-mask (''*''))
***


rm -r /etc/default/xendomains
touch /etc/default/xendomains
nano /etc/default/xendomains

***
XENDOMAINS_SYSRQ=""
XENDOMAINS_USLEEP=100000
XENDOMAINS_CREATE_USLEEP=5000000
XENDOMAINS_MIGRATE=""
XENDOMAINS_SAVE=/var/lib/xen/save
XENDOMAINS_SHUTDOWN="--halt --wait"
XENDOMAINS_SHUTDOWN_ALL="--all --halt --wait"
XENDOMAINS_RESTORE=false
XENDOMAINS_AUTO=/etc/xen/auto
XENDOMAINS_AUTO_ONLY=true
XENDOMAINS_STOP_MAXWAIT=500
***


rm -r /etc/default/grub
touch /etc/default/grub
nano /etc/default/grub

***
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
#GRUB_TERMINAL=console
#GRUB_GFXMODE=640x480
#GRUB_DISABLE_LINUX_UUID=true
#GRUB_DISABLE_LINUX_RECOVERY=true
GRUB_DISABLE_OS_PROBER=true
#GRUB_INIT_TUNE="480 440 1"
***


rm -r /etc/grub.d/08_xen
touch /etc/grub.d/08_xen
nano /etc/grub.d/08_xen

***
#!/bin/sh
exec tail -n +3 $0
menuentry "Xen 4.2 Unstable / Debian Squeeze kernel 3.0.0" {
        insmod ext2
        insmod multiboot2
        insmod lvm
        insmod part_msdos
        insmod raid
        insmod mdraid
        set root=''(md/1)''
        search --no-floppy --fs-uuid --set [UUID]
        echo ''Loading multiboot kernel ...''
        multiboot (md/1)/boot/xen.gz placeholder dom0_mem=1024M
        echo ''Loading initial kernel ...''
        module (md/1)/boot/vmlinuz-3.0.0 placeholder root=UUID=[UUID] ro
quiet console=tty0 nomodeset
        echo ''Loading initial ramdisk ...''
        module (md/1)/boot/initrd.img-3.0.0
}
***


chmod -x /etc/grub.d/20_linux_xen
chmod 755 /etc/grub.d/08_xen
update-grub2

update-rc.d xencommons defaults 19 18
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20

/etc/init.d/xencommons start
/etc/init.d/xend start
/etc/init.d/xendomains start


rm -r /etc/modules
touch /etc/modules
nano /etc/modules

***
loop max_loop=64
lp
rtc
xen-evtchn
xen-gntdev
xen-netback
xen-blkback
xenfs
blktap
***


rm -r /etc/xen/server02.cfg
touch /etc/xen/server02.cfg
nano /etc/xen/server02.cfg

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

uuid            = ''[UUID]''

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

#disk           = [
''phy:/dev/vgmain/lv_server01,hda,w'',''file:/var/xen/debian-6.0.2.1-amd64-neti
nst.iso,hdc:cdrom,r'' ]
disk            = [ ''phy:/dev/vgmain/lv_server01,hda,w'' ]

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: Mark Schneider [mailto:ms@it-infrastrukturen.org] 
Sent: Dienstag, 26. Juli 2011 00:09
To: Walter Robert Ditzler
Subject: Re: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card
error

Walter,

where can I find these two files? (kernel config and your "how to do"?

Thank you / regards
Mark


Am 25.07.2011 01:04, schrieb Walter Robert Ditzler:
> nope, but have all documented in 2 txt file, 1 is the kernel config 
> and the other a complete install after having a running virgin squeeze
box.
> checkinstall made problems.
>
> thanks walter
>
> -----Original Message-----
> From: Mark Schneider [mailto:ms@it-infrastrukturen.org]
> Sent: Sonntag, 24. Juli 2011 23:33
> To: Walter Robert Ditzler; xen-devel@lists.xensource.com
> Subject: 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@gmail.com]
>> Sent: Mittwoch, 20. Juli 2011 14:09
>> To: ''Stefano Stabellini''
>> Cc: konrad.wilk@oracle.com; xen-devel@lists.xensource.com; 
>> xen-users@lists.xensource.com
>> 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-amd6
>> 4
>> -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-amd6
>> 4
>> -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@eu.citrix.com]
>> Sent: Mittwoch, 20. Juli 2011 13:40
>> To: Walter Robert Ditzler
>> Cc: Stefano Stabellini; konrad.wilk@oracle.com; 
>> xen-devel@lists.xensource.com; xen-users@lists.xensource.com
>> 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-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

.. snip..
> I need the output of the guest kernel stuck during boot in order to
> understand the problem. It shouldn''t be difficult to get if you
enable
> logging over the serial in the guest kernel.
Hey Stefano,

Looks like I can reproduce this as well. This is using Fedora Core 16,
and with the Fedora Core 16 HVM install.

The interesting thing is that while ''xl'' works, the
''xm'' (which is what
virt-install and all of that uses), does not. And I think it is related
just to how we handle the hdc:cdrom,r case. Read below.

Just to make sure it is not SELinux related, I''ve called
''setenforce=0''.
The guest config is easy:

kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory=1024
#maxmem=1024
maxvcpus = 2
serial=''pty''
vcpus = 2
disk = [ ''file:/mnt/iso/Fedora-16-x86_64-DVD.iso,hdc:cdrom,r'',
''phy:/dev/vg_guest/f16_64,hda,w'']
boot="dn"
vif = [ ''type=ioemu,model=e1000,mac=00:0F:4B:00:00:71,
bridge=switch'' ]
vfb = [ ''vnc=1, vnclisten=0.0.0.0 ,vncunused=1'']
vnclisten="0.0.0.0"

Attached are the serial logs from good and bad, and as well the xenstore-ls from
..
you guessed it - good and bad. The interesting part is:

(this works)
   backend = ""
    qdisk = ""
     24 = ""
      5632 = ""
       frontend = "/local/domain/24/device/vbd/5632"
       params = "aio:/mnt/iso/Fedora-16-x86_64-DVD.iso"
       frontend-id = "24"
       online = "1"
       removable = "1"
       bootable = "1"
       state = "6"
       dev = "hdc"
       type = "tap"
       mode = "r"
       feature-barrier = "1"
       info = "4"
       sector-size = "512"
       sectors = "7337984"
       hotplug-status = "connected"

(this fails)
    vbd = ""
     10 = ""
      768 = ""
       domain = "test"
       frontend = "/local/domain/10/device/vbd/768"
       uuid = "ee7800e1-fae0-dfe2-9345-96fda7d7851f"
       bootable = "1"
       dev = "hda"
       state = "4"
       params = "/var/lib/xen/images/test.img"
       mode = "w"
       online = "1"
       frontend-id = "10"
       type = "file"
       node = "/dev/loop0"
       physical-device = "7:0"
       hotplug-status = "connected"
       feature-flush-cache = "1"
       sectors = "41943040"
       info = "0"
       sector-size = "512"

Which would imply that for the CD-ROM when we use ''xm'' it is
setup
as a PV disk (and we try to load the driver for it but fail)
while for the ''xl'' it is as a QEMU qdisk (so emulated).

First I *thought* it was that blkback is failing to do its
stuff when using /dev/loop0, but after doing this:

disk = [ ''phy:/dev/loop0,hda,w'']

I still got it to boot.

So it really seams that xen-blkback (or xen-blkfront) can''t deal
with CD-ROMs very well. So I did it:

disk = [ ''phy:/dev/loop1,hdc:cdrom,r'',
''phy:/dev/loop0,hda,w'']
[root@phenom ~]# losetup -a
/dev/loop0: [0005]:1353 (/dev/mapper/vg_guest-f16_64)
/dev/loop1: [002a]:45613764 (/mnt/iso/Fedora-16-x86_64-DVD.iso)

Which is pretty much exactly what the ''file:/''.. would, and I
got this
 vbd = ""
     34 = ""
      5632 = ""
       domain = "hvm.xm"
       frontend = "/local/domain/34/device/vbd/5632"
       uuid = "e30da140-7ef9-9c1f-8e45-1e5e63f798e0"
       bootable = "1"
       dev = "hdc"
       state = "6"
       params = "/dev/loop1"
       mode = "r"
       online = "1"
       frontend-id = "34"
       type = "phy"
       physical-device = "7:1"
       hotplug-status = "connected"

And after waiting for the timeout.. (can''t load and then some more, the
installer
came up and I could ''Test'' the ISO image. The CD-ROM image was
emulated, which sounds right - the vbd/34/5632 just did not work out
and it timed out, but it still had the QEMU disk (/dev/sr0) and it used
that instead.

Any suggestions, thoughts, ideas? It sounds like the xen-blkfront
support for CD-ROMs is not working right.

Or maybe there are multiple issues and the error from xen-blkfront is
red heering. I seem to see other things too:

vif vif-0: 2 parsing device/vif/0/mac

[Ugh, looks like MAC is 00:00:00:0.. in the guest], but it probably got the
right
MAC on the emulated device]


XENBUS: Timeout connecting to device: device/vkbd/0 (local state 3, remote state
1)
[which seems odds as the vkb from VNC looks to be working]






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

On Thu, 3 Nov 2011, Konrad Rzeszutek Wilk wrote:
> .. snip..
> > I need the output of the guest kernel stuck during boot in order to
> > understand the problem. It shouldn''t be difficult to get if
you enable
> > logging over the serial in the guest kernel.
> 
> Hey Stefano,
> 
> Looks like I can reproduce this as well. This is using Fedora Core 16,
> and with the Fedora Core 16 HVM install.
> 
> The interesting thing is that while ''xl'' works, the
''xm'' (which is what
> virt-install and all of that uses), does not. And I think it is related
> just to how we handle the hdc:cdrom,r case. Read below.
> 
> Just to make sure it is not SELinux related, I''ve called
''setenforce=0''.
> The guest config is easy:
> 
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder=''hvm''
> memory=1024
> #maxmem=1024
> maxvcpus = 2
> serial=''pty''
> vcpus = 2
> disk = [
''file:/mnt/iso/Fedora-16-x86_64-DVD.iso,hdc:cdrom,r'',
''phy:/dev/vg_guest/f16_64,hda,w'']
> boot="dn"
> vif = [ ''type=ioemu,model=e1000,mac=00:0F:4B:00:00:71,
bridge=switch'' ]
> vfb = [ ''vnc=1, vnclisten=0.0.0.0 ,vncunused=1'']
> vnclisten="0.0.0.0"
BTW the vfb setting is wrong for an hvm domain.
The correct way of configuring vnc is the following:

vnc=1
vnclisten="0.0.0.0"
vncunused=1

it just happened to work with xm but it was never supposed to.

> Attached are the serial logs from good and bad, and as well the xenstore-ls
from ..
> you guessed it - good and bad. The interesting part is:
> 
> (this works)
>    backend = ""
>     qdisk = ""
>      24 = ""
>       5632 = ""
>        frontend = "/local/domain/24/device/vbd/5632"
>        params = "aio:/mnt/iso/Fedora-16-x86_64-DVD.iso"
>        frontend-id = "24"
>        online = "1"
>        removable = "1"
>        bootable = "1"
>        state = "6"
>        dev = "hdc"
>        type = "tap"
>        mode = "r"
>        feature-barrier = "1"
>        info = "4"
>        sector-size = "512"
>        sectors = "7337984"
>        hotplug-status = "connected"
> 
> (this fails)
>     vbd = ""
>      10 = ""
>       768 = ""
>        domain = "test"
>        frontend = "/local/domain/10/device/vbd/768"
>        uuid = "ee7800e1-fae0-dfe2-9345-96fda7d7851f"
>        bootable = "1"
>        dev = "hda"
>        state = "4"
>        params = "/var/lib/xen/images/test.img"
>        mode = "w"
>        online = "1"
>        frontend-id = "10"
>        type = "file"
>        node = "/dev/loop0"
>        physical-device = "7:0"
>        hotplug-status = "connected"
>        feature-flush-cache = "1"
>        sectors = "41943040"
>        info = "0"
>        sector-size = "512"
> 
> Which would imply that for the CD-ROM when we use ''xm'' it
is setup
> as a PV disk (and we try to load the driver for it but fail)
> while for the ''xl'' it is as a QEMU qdisk (so emulated).
There is always a PV disk associated with CD-ROMs even though the guest
is not going to use it. Linux blkfront would explicitly avoid to setup
a PV interface for CD-ROMs.

> First I *thought* it was that blkback is failing to do its
> stuff when using /dev/loop0, but after doing this:
> 
> disk = [ ''phy:/dev/loop0,hda,w'']
> 
> I still got it to boot.
Let me get this straight:

disk = [ ''phy:/dev/loop0,hda,w''] works
disk = [ ''file:/mnt/iso/Fedora-16-x86_64-DVD.iso,hdc:cdrom,r''
] does NOT work

that is very strange considering that if I recall correctly xm/xend
would setup a loop device when the disk config is ''file:'', so
the two
should be equivalent.

> So it really seams that xen-blkback (or xen-blkfront) can''t deal
> with CD-ROMs very well. So I did it:
> 
> disk = [ ''phy:/dev/loop1,hdc:cdrom,r'',
''phy:/dev/loop0,hda,w'']
> [root@phenom ~]# losetup -a
> /dev/loop0: [0005]:1353 (/dev/mapper/vg_guest-f16_64)
> /dev/loop1: [002a]:45613764 (/mnt/iso/Fedora-16-x86_64-DVD.iso)
> 
> Which is pretty much exactly what the ''file:/''.. would,
and I got this
>  vbd = ""
>      34 = ""
>       5632 = ""
>        domain = "hvm.xm"
>        frontend = "/local/domain/34/device/vbd/5632"
>        uuid = "e30da140-7ef9-9c1f-8e45-1e5e63f798e0"
>        bootable = "1"
>        dev = "hdc"
>        state = "6"
>        params = "/dev/loop1"
>        mode = "r"
>        online = "1"
>        frontend-id = "34"
>        type = "phy"
>        physical-device = "7:1"
>        hotplug-status = "connected"
> 
> And after waiting for the timeout.. (can''t load and then some
more, the installer
> came up and I could ''Test'' the ISO image. The CD-ROM
image was
> emulated, which sounds right - the vbd/34/5632 just did not work out
> and it timed out, but it still had the QEMU disk (/dev/sr0) and it used
> that instead.
What is the guest kernel? As I said before blkfront should avoid loading
a PV disk for CD-ROMs, see:

commit b98a409b80ac510c95b4f1bafdef28edaeabd3e7
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date:   Thu Jul 29 14:53:16 2010 +0100

    blkfront: do not create a PV cdrom device if xen_hvm_guest
    
    It is not possible to unplug emulated cdrom devices, and PV cdroms
don''t
    handle media insert, eject and stream, so we are better off disabling PV
    cdroms when running as a Xen HVM guest.
    
    Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> Any suggestions, thoughts, ideas? It sounds like the xen-blkfront
> support for CD-ROMs is not working right.
it shouldn''t work at all :)

> Or maybe there are multiple issues and the error from xen-blkfront is
> red heering. I seem to see other things too:
> 
> vif vif-0: 2 parsing device/vif/0/mac
> 
> [Ugh, looks like MAC is 00:00:00:0.. in the guest], but it probably got the
right
> MAC on the emulated device]
> 
> 
> XENBUS: Timeout connecting to device: device/vkbd/0 (local state 3, remote
state 1)
> [which seems odds as the vkb from VNC looks to be working]
Thanks for pointing this out: I enabled vkbd in upstream qemu but I
forgot to do the same in qemu-xen so as a result you would get failures
of this kind.

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

On Mon, Nov 07, 2011 at 05:15:08PM +0000, Stefano Stabellini
wrote:
> On Thu, 3 Nov 2011, Konrad Rzeszutek Wilk wrote:
> > .. snip..
> > > I need the output of the guest kernel stuck during boot in order
to
> > > understand the problem. It shouldn''t be difficult to get
if you enable
> > > logging over the serial in the guest kernel.
> > 
> > Hey Stefano,
> > 
> > Looks like I can reproduce this as well. This is using Fedora Core 16,
> > and with the Fedora Core 16 HVM install.
> > 
> > The interesting thing is that while ''xl'' works, the
''xm'' (which is what
> > virt-install and all of that uses), does not. And I think it is
related
> > just to how we handle the hdc:cdrom,r case. Read below.
> > 
> > Just to make sure it is not SELinux related, I''ve called
''setenforce=0''.
> > The guest config is easy:
> > 
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder=''hvm''
> > memory=1024
> > #maxmem=1024
> > maxvcpus = 2
> > serial=''pty''
> > vcpus = 2
> > disk = [
''file:/mnt/iso/Fedora-16-x86_64-DVD.iso,hdc:cdrom,r'',
''phy:/dev/vg_guest/f16_64,hda,w'']
> > boot="dn"
> > vif = [ ''type=ioemu,model=e1000,mac=00:0F:4B:00:00:71,
bridge=switch'' ]
> > vfb = [ ''vnc=1, vnclisten=0.0.0.0 ,vncunused=1'']
> > vnclisten="0.0.0.0"
> 
> BTW the vfb setting is wrong for an hvm domain.
> The correct way of configuring vnc is the following:
> 
> vnc=1
> vnclisten="0.0.0.0"
> vncunused=1
> 
> it just happened to work with xm but it was never supposed to.
> 
> 
> > Attached are the serial logs from good and bad, and as well the
xenstore-ls from ..
> > you guessed it - good and bad. The interesting part is:
> > 
> > (this works)
> >    backend = ""
> >     qdisk = ""
> >      24 = ""
> >       5632 = ""
> >        frontend = "/local/domain/24/device/vbd/5632"
> >        params = "aio:/mnt/iso/Fedora-16-x86_64-DVD.iso"
> >        frontend-id = "24"
> >        online = "1"
> >        removable = "1"
> >        bootable = "1"
> >        state = "6"
> >        dev = "hdc"
> >        type = "tap"
> >        mode = "r"
> >        feature-barrier = "1"
> >        info = "4"
> >        sector-size = "512"
> >        sectors = "7337984"
> >        hotplug-status = "connected"
> > 
> > (this fails)
> >     vbd = ""
> >      10 = ""
> >       768 = ""
> >        domain = "test"
> >        frontend = "/local/domain/10/device/vbd/768"
> >        uuid = "ee7800e1-fae0-dfe2-9345-96fda7d7851f"
> >        bootable = "1"
> >        dev = "hda"
> >        state = "4"
> >        params = "/var/lib/xen/images/test.img"
> >        mode = "w"
> >        online = "1"
> >        frontend-id = "10"
> >        type = "file"
> >        node = "/dev/loop0"
> >        physical-device = "7:0"
> >        hotplug-status = "connected"
> >        feature-flush-cache = "1"
> >        sectors = "41943040"
> >        info = "0"
> >        sector-size = "512"
> > 
> > Which would imply that for the CD-ROM when we use
''xm'' it is setup
> > as a PV disk (and we try to load the driver for it but fail)
> > while for the ''xl'' it is as a QEMU qdisk (so
emulated).
> 
> There is always a PV disk associated with CD-ROMs even though the guest
> is not going to use it. Linux blkfront would explicitly avoid to setup
> a PV interface for CD-ROMs.
> 
> 
> > First I *thought* it was that blkback is failing to do its
> > stuff when using /dev/loop0, but after doing this:
> > 
> > disk = [ ''phy:/dev/loop0,hda,w'']
> > 
> > I still got it to boot.
> 
> Let me get this straight:
> 
> disk = [ ''phy:/dev/loop0,hda,w''] works
> disk = [
''file:/mnt/iso/Fedora-16-x86_64-DVD.iso,hdc:cdrom,r'' ] does
NOT work
> 
> that is very strange considering that if I recall correctly xm/xend
> would setup a loop device when the disk config is
''file:'', so the two
> should be equivalent.
<nods> It might have been me getting tired by this point. The timeout
seems
to be .. well, I think that the ''file'' works as well - it is
just that the
timeout takes forever, and then there might be another timeout before the
anaconda windows pops up. So it could be that in the normal case it works - it
just that you have to be patient.
> 
> 
> > So it really seams that xen-blkback (or xen-blkfront) can''t
deal
> > with CD-ROMs very well. So I did it:
> > 
> > disk = [ ''phy:/dev/loop1,hdc:cdrom,r'',
''phy:/dev/loop0,hda,w'']
> > [root@phenom ~]# losetup -a
> > /dev/loop0: [0005]:1353 (/dev/mapper/vg_guest-f16_64)
> > /dev/loop1: [002a]:45613764 (/mnt/iso/Fedora-16-x86_64-DVD.iso)
> > 
> > Which is pretty much exactly what the ''file:/''..
would, and I got this
> >  vbd = ""
> >      34 = ""
> >       5632 = ""
> >        domain = "hvm.xm"
> >        frontend = "/local/domain/34/device/vbd/5632"
> >        uuid = "e30da140-7ef9-9c1f-8e45-1e5e63f798e0"
> >        bootable = "1"
> >        dev = "hdc"
> >        state = "6"
> >        params = "/dev/loop1"
> >        mode = "r"
> >        online = "1"
> >        frontend-id = "34"
> >        type = "phy"
> >        physical-device = "7:1"
> >        hotplug-status = "connected"
> > 
> > And after waiting for the timeout.. (can''t load and then some
more, the installer
> > came up and I could ''Test'' the ISO image. The CD-ROM
image was
> > emulated, which sounds right - the vbd/34/5632 just did not work out
> > and it timed out, but it still had the QEMU disk (/dev/sr0) and it
used
> > that instead.
> 
> What is the guest kernel? As I said before blkfront should avoid loading
> a PV disk for CD-ROMs, see:
F16 DomU. So 3.1
> 
> commit b98a409b80ac510c95b4f1bafdef28edaeabd3e7
> Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Date:   Thu Jul 29 14:53:16 2010 +0100
> 
>     blkfront: do not create a PV cdrom device if xen_hvm_guest
>     
>     It is not possible to unplug emulated cdrom devices, and PV cdroms
don''t
>     handle media insert, eject and stream, so we are better off disabling
PV
>     cdroms when running as a Xen HVM guest.
>     
>     Signed-off-by: Stefano Stabellini
<stefano.stabellini@eu.citrix.com>
> 
> 
> > Any suggestions, thoughts, ideas? It sounds like the xen-blkfront
> > support for CD-ROMs is not working right.
> 
> it shouldn''t work at all :)
HA!
> 
> 
> > Or maybe there are multiple issues and the error from xen-blkfront is
> > red heering. I seem to see other things too:
> > 
> > vif vif-0: 2 parsing device/vif/0/mac
> > 
> > [Ugh, looks like MAC is 00:00:00:0.. in the guest], but it probably
got the right
> > MAC on the emulated device]
> > 
> > 
> > XENBUS: Timeout connecting to device: device/vkbd/0 (local state 3,
remote state 1)
> > [which seems odds as the vkb from VNC looks to be working]
> 
> Thanks for pointing this out: I enabled vkbd in upstream qemu but I
> forgot to do the same in qemu-xen so as a result you would get failures
> of this kind.
Oh boy. Seems that there are a couple of issues here. It might be that the
timeout I had experienced was _only_ related to this and the other were
red-herrings.

You might want to make sure M A Young and Stefan Bader are CC-ed on your Xen
4.1.1
patch so they can pull it in.

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

On Mon, 7 Nov 2011, Konrad Rzeszutek Wilk wrote:
> > > XENBUS: Timeout connecting to device: device/vkbd/0 (local state
3, remote state 1)
> > > [which seems odds as the vkb from VNC looks to be working]
> > 
> > Thanks for pointing this out: I enabled vkbd in upstream qemu but I
> > forgot to do the same in qemu-xen so as a result you would get
failures
> > of this kind.
> 
> Oh boy. Seems that there are a couple of issues here. It might be that the
> timeout I had experienced was _only_ related to this and the other were
red-herrings.
> 
> You might want to make sure M A Young and Stefan Bader are CC-ed on your
Xen 4.1.1
> patch so they can pull it in.
Actually I have just realized that the vkbd feature couldn''t possibly
have been backported to xen 4.1.1. In fact I didn''t even add any vkbd
devices for HVM guests in XL in xen-unstable yet.
Of course this was to avoid situations like this one.

So my guess is that when you use "vfb" in an HVM guest config file
you cause xend to create a vkbd device that is without backend.
A PV on HVM guest would try to connect to it but it wouldn''t get any
response back so it would timeout.

The solution to this problem is to avoid using vfb in the config file. I
strongly hope that the config file you showed us before is not generated
by libvirt somehow. If it is we need to file a bug against libvirt.

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

On Tue, Nov 08, 2011 at 11:09:11AM +0000, Stefano Stabellini
wrote:
> On Mon, 7 Nov 2011, Konrad Rzeszutek Wilk wrote:
> > > > XENBUS: Timeout connecting to device: device/vkbd/0 (local
state 3, remote state 1)
> > > > [which seems odds as the vkb from VNC looks to be working]
> > > 
> > > Thanks for pointing this out: I enabled vkbd in upstream qemu but
I
> > > forgot to do the same in qemu-xen so as a result you would get
failures
> > > of this kind.
> > 
> > Oh boy. Seems that there are a couple of issues here. It might be that
the
> > timeout I had experienced was _only_ related to this and the other
were red-herrings.
> > 
> > You might want to make sure M A Young and Stefan Bader are CC-ed on
your Xen 4.1.1
> > patch so they can pull it in.
> 
> Actually I have just realized that the vkbd feature couldn''t
possibly
> have been backported to xen 4.1.1. In fact I didn''t even add any
vkbd
> devices for HVM guests in XL in xen-unstable yet.
> Of course this was to avoid situations like this one.
> 
> So my guess is that when you use "vfb" in an HVM guest config
file
> you cause xend to create a vkbd device that is without backend.
> A PV on HVM guest would try to connect to it but it wouldn''t get
any
> response back so it would timeout.
> 
> The solution to this problem is to avoid using vfb in the config file. I
> strongly hope that the config file you showed us before is not generated
> by libvirt somehow. If it is we need to file a bug against libvirt.
It looks like it is:

[root@phenom Mail]# virsh dumpxml f16_64 > /tmp/a
[root@phenom Mail]# virsh  domxml-to-native xen-xm /tmp/a
name = "f16_64"
uuid = "587ea6cf-8296-a4d3-86e2-d8afa991bd4b"
maxmem = 1024
memory = 1024
vcpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
hap = 0
viridian = 0
localtime = 0
hpet = 0
on_poweroff = "destroy"
on_reboot = "destroy"
on_crash = "destroy"
device_model = "/usr/lib64/xen/bin/qemu-dm"
vfb = [ "type=vnc,vncunused=1,keymap=en-us" ]
disk = [ "phy:/dev/vg_guest/f16_64,hda,w",
"file:/mnt/iso/Fedora-16-x86_64-DVD.iso,hdc:cdrom,r" ]
vif = [
"mac=00:16:3e:44:07:4b,bridge=switch,script=vif-bridge,vifname=vif7.0"
]
parallel = "none"
serial = "pty"

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

On Tue, Nov 08, 2011 at 11:09:11AM +0000, Stefano Stabellini
wrote:
> On Mon, 7 Nov 2011, Konrad Rzeszutek Wilk wrote:
> > > > XENBUS: Timeout connecting to device: device/vkbd/0 (local
state 3, remote state 1)
> > > > [which seems odds as the vkb from VNC looks to be working]
> > > 
> > > Thanks for pointing this out: I enabled vkbd in upstream qemu but
I
> > > forgot to do the same in qemu-xen so as a result you would get
failures
> > > of this kind.
> > 
> > Oh boy. Seems that there are a couple of issues here. It might be that
the
> > timeout I had experienced was _only_ related to this and the other
were red-herrings.
> > 
> > You might want to make sure M A Young and Stefan Bader are CC-ed on
your Xen 4.1.1
> > patch so they can pull it in.
> 
> Actually I have just realized that the vkbd feature couldn''t
possibly
> have been backported to xen 4.1.1. In fact I didn''t even add any
vkbd
> devices for HVM guests in XL in xen-unstable yet.
> Of course this was to avoid situations like this one.
> 
> So my guess is that when you use "vfb" in an HVM guest config
file
> you cause xend to create a vkbd device that is without backend.
> A PV on HVM guest would try to connect to it but it wouldn''t get
any
> response back so it would timeout.
> 
> The solution to this problem is to avoid using vfb in the config file. I
> strongly hope that the config file you showed us before is not generated
> by libvirt somehow. If it is we need to file a bug against libvirt.
And sure enough, if I modify the xm file libvirt creates to be:

[root@phenom ~]# diff /tmp/b.autogenerated /tmp/b
8c8
< boot = "c"
---
> boot = "dc"
20c20,21
< vfb = [ "type=vnc,vncunused=1" ]
---
> #vfb = [ "type=vnc,vncunused=1,keymap=en-us" ]
> vnc=1

It bootes right up. Is this a new behavior with xend? I would think
not - it just seems that the ''vfb'' for HVM guests worked in
the past -
as Windows boots just fine? And I think the accelerated drivers
for Windows take advantage of that?

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

On Thu, 10 Nov 2011, Konrad Rzeszutek Wilk wrote:
> On Tue, Nov 08, 2011 at 11:09:11AM +0000, Stefano Stabellini wrote:
> > On Mon, 7 Nov 2011, Konrad Rzeszutek Wilk wrote:
> > > > > XENBUS: Timeout connecting to device: device/vkbd/0
(local state 3, remote state 1)
> > > > > [which seems odds as the vkb from VNC looks to be
working]
> > > > 
> > > > Thanks for pointing this out: I enabled vkbd in upstream
qemu but I
> > > > forgot to do the same in qemu-xen so as a result you would
get failures
> > > > of this kind.
> > > 
> > > Oh boy. Seems that there are a couple of issues here. It might be
that the
> > > timeout I had experienced was _only_ related to this and the
other were red-herrings.
> > > 
> > > You might want to make sure M A Young and Stefan Bader are CC-ed
on your Xen 4.1.1
> > > patch so they can pull it in.
> > 
> > Actually I have just realized that the vkbd feature couldn''t
possibly
> > have been backported to xen 4.1.1. In fact I didn''t even add
any vkbd
> > devices for HVM guests in XL in xen-unstable yet.
> > Of course this was to avoid situations like this one.
> > 
> > So my guess is that when you use "vfb" in an HVM guest
config file
> > you cause xend to create a vkbd device that is without backend.
> > A PV on HVM guest would try to connect to it but it wouldn''t
get any
> > response back so it would timeout.
> > 
> > The solution to this problem is to avoid using vfb in the config file.
I
> > strongly hope that the config file you showed us before is not
generated
> > by libvirt somehow. If it is we need to file a bug against libvirt.
> 
> And sure enough, if I modify the xm file libvirt creates to be:
> 
> [root@phenom ~]# diff /tmp/b.autogenerated /tmp/b
> 8c8
> < boot = "c"
> ---
> > boot = "dc"
> 20c20,21
> < vfb = [ "type=vnc,vncunused=1" ]
> ---
> > #vfb = [ "type=vnc,vncunused=1,keymap=en-us" ]
> > vnc=1
> 
> 
> It bootes right up. Is this a new behavior with xend? I would think
> not - it just seems that the ''vfb'' for HVM guests worked
in the past -
> as Windows boots just fine? And I think the accelerated drivers
> for Windows take advantage of that?
> 
Have you noticed that the vnc parameters inside vfb look very similar to
the normal vnc parameters outside vfb?
Xend happens to store both set of vnc parameters the same way, using
the same internal variables. That is why it happened to work in the
past. It was working by pure chance, I have no idea what changed.
Windows doesn''t take advance of vfb or vkbd at all.

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