All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Walter Robert Ditzler" <ditwal001@gmail.com>
To: 'Stefano Stabellini' <stefano.stabellini@eu.citrix.com>,
	konrad.wilk@oracle.com
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: RE: xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card error
Date: Tue, 19 Jul 2011 20:56:49 +0200	[thread overview]
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAE0cphS4zTVFjzXOjWNB7uwBAAAAAA==@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1107181242270.12963@kaball-desktop>

[-- Attachment #1: Type: text/plain, Size: 5010 bytes --]

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.



[-- Attachment #2: server01_debian-installer-1.JPG --]
[-- Type: image/jpeg, Size: 41488 bytes --]

[-- Attachment #3: server01_debian-installer-2.JPG --]
[-- Type: image/jpeg, Size: 40846 bytes --]

[-- Attachment #4: server01_debian-installer-3.JPG --]
[-- Type: image/jpeg, Size: 70373 bytes --]

[-- Attachment #5: server02_xen_win7.JPG --]
[-- Type: image/jpeg, Size: 61350 bytes --]

[-- Attachment #6: qemu-dm-server01.log --]
[-- Type: application/octet-stream, Size: 1810 bytes --]

domid: 26
Using file /dev/vgmain/lv_server01 in read-write mode
Strip off blktap sub-type prefix to /var/xen/debian-6.0.1a-amd64-netinst.iso (drv 'aio')
Using file /var/xen/debian-6.0.1a-amd64-netinst.iso in read-only mode
Watching /local/domain/0/device-model/26/logdirty/cmd
Watching /local/domain/0/device-model/26/command
Watching /local/domain/26/cpu
char device redirected to /dev/pts/4
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 1d4d176d-fe36-48e3-aaf5-57d07f588b4b
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/26/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/1d4d176d-fe36-48e3-aaf5-57d07f588b4b/vncpasswd.
medium change watch on `hdc' (index: 1): aio:/var/xen/debian-6.0.1a-amd64-netinst.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/26/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/26/log-throttling'
medium change watch on `/local/domain/26/log-throttling' - unknown device, ignored
vga s->lfb_addr = f1000000 s->lfb_end = f1800000 
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
mapping vram to f1000000 - f1800000
Unknown PV product 3 loaded in guest
PV driver build 1
region type 1 at [c100,c200).
region type 0 at [f1800000,f1800100).
squash iomem [f1000000, f1800000).
vga s->lfb_addr = f1000000 s->lfb_end = f1800000 

[-- Attachment #7: qemu-dm-server02.log --]
[-- Type: application/octet-stream, Size: 1450 bytes --]

domid: 23
Using file /dev/vgmain/lv_server02 in read-write mode
Watching /local/domain/0/device-model/23/logdirty/cmd
Watching /local/domain/0/device-model/23/command
Watching /local/domain/23/cpu
char device redirected to /dev/pts/2
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = a39e255d-4cd5-4d94-a0c4-19839718df43
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/23/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/a39e255d-4cd5-4d94-a0c4-19839718df43/vncpasswd.
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
xs_read(/local/domain/23/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/23/log-throttling'
medium change watch on `/local/domain/23/log-throttling' - unknown device, ignored
vga s->lfb_addr = f1000000 s->lfb_end = f1800000 
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
mapping vram to f1000000 - f1800000
vga s->lfb_addr = f1000000 s->lfb_end = f1800000 
vga s->lfb_addr = f1000000 s->lfb_end = f1800000 

[-- Attachment #8: xl-server01.log --]
[-- Type: application/octet-stream, Size: 58 bytes --]

Waiting for domain server01 (domid 26) to die [pid 7421]

[-- Attachment #9: Type: text/plain, Size: 138 bytes --]

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

  parent reply	other threads:[~2011-07-19 18:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17 18:00 xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card error Walter Robert Ditzler
2011-07-18 11:47 ` [Xen-devel] " Stefano Stabellini
2011-07-18 15:03   ` Konrad Rzeszutek Wilk
2011-07-19 18:56   ` Walter Robert Ditzler [this message]
2011-07-20 11:40     ` Stefano Stabellini
2011-07-20 12:08       ` Walter Robert Ditzler
2011-07-24 22:21         ` Walter Robert Ditzler
2011-07-24 21:33           ` Mark Schneider
2011-07-24 23:04             ` Walter Robert Ditzler
2011-07-25 10:42           ` Stefano Stabellini
2011-07-25 11:25             ` Walter Robert Ditzler
2011-07-25 16:50               ` Stefano Stabellini
2011-11-03 17:38                 ` Is: Xen 4.1.1, xend, HVM, 3.1 kernel; Was:Re: " Konrad Rzeszutek Wilk
2011-11-07 17:15                   ` Stefano Stabellini
2011-11-07 21:26                     ` Konrad Rzeszutek Wilk
2011-11-08 11:09                       ` Stefano Stabellini
2011-11-10 17:02                         ` Konrad Rzeszutek Wilk
2011-11-10 17:14                         ` Konrad Rzeszutek Wilk
2011-11-10 17:20                           ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=''\!'&'\!'AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAE0cphS4zTVFjzXOjWNB7uwBAAAAAA==@gmail.com' \
    --to=ditwal001@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.