On Sun July 17 2011 3:52:48 PM you wrote:
> hi jim,
>
> i just posted a thread several hours ago about xen 4.2 unstable, 2.6.39.3
> and problem creating hvm guest's. I would be interested if you have more
> details why there are problems. my problem actually is that my guest's
> cant access hw resources from dom0!
This looks like a very different problem. Let's see what jumps out at me:
from dmesg: (looks like dom0 to me)
> [ 0.000000] Kernel command line: dummy root=UUID=6d870fbe-f4a5-4aa6-
bc2f-502f81344e7b ro quiet console=tty0 nomodeset
Ah yes, grub*2*, sigh!
> [ 0.041309] ACPI: EC: Look up EC in DSDT
> [ 0.042064] ACPI Error: Field [CDW3] at 96 exceeds Buffer [NULL] size 64
> (bits) (20110316/dsopcode-236)
> [ 0.042081] ACPI Error: Method parse/execution failed [\_SB_._OSC] (Node
ffff8800319119c0), AE_AML_BUFFER_LIMIT (20110316/psparse-536)
> [ 0.046996] ACPI: Interpreter enabled
> [ 0.046996] ACPI: (supports S0 S5)
> [ 0.047028] ACPI: Using PIC for interrupt routing
This bothers me that your dom0 can't initialize acpi w/o errors. Maybe that's
why you chose 'acpi=0' in your hvm config. (Btw, use hda/hdc in your disk=
line, not xvda/xvdc, though xen *should* translate for you.)
> [ 0.263779] Failed to setup GSI :1, err_code:-22
Lot of dom0 errors of this form. Any hardware problems on dom0 itself?
From 'qemu-dm':
> qemu: ignoring not-understood drive `xvda'
Reinforces my comment above. Everything else looks ok here.
From xen-hotplug:
> RTNETLINK answers: Operation not supported
> /etc/xen/scripts/xen-network-common.sh: line 131: brctl: command not found
> /etc/xen/scripts/xen-network-common.sh: line 131: brctl: command not found
Ah ha! Nothing is going to work if you don't have bridge utils installed.
Also, make sure 'brctl' is in the PATH.
From your xl log:
Each 'xl create' ends in a lot of 'int13_harddisk:' errors. Possibly also from
the xvda/hda mixup. Also, your server02 config says 'boot='cd', but your xl
log says:
> Boot from Hard Disk failed: could not read the boot disk
and then tries to boot from the cd. Don't know why you didn't see anything
from the cd, tho'. (You had the cd inserted, right?)
Scratch that - I just saw you're accessing the .iso file on /var/xen with a
'phy:' prefix. It should be 'file:'. (Or some variation of tap: or tap2:.
However, since 3.0.0 doesn't have blktap.ko, I doubt that 2.6.39.3 does,
unless Debian added it themselves.)
I'm going to assume that some of your dom0 dmesg errors are because xen 4.2 is
still 'unstable'. I haven't worked with 4.2 yet.
Hope this helped. Good luck.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home