Re: [Xen-users] Can't boot HVM Linux guests on Debian Squeeze Dom0

[Garrett Robinson <Garrett.Robinson@xxxxxxxxxxx>]

Hey John,

I tried both of your suggestions. Neither of them worked, unfortunately.

With 'tap2:tapdisk:aio:', I got the following error almost immediately:

# xm create 343-3-0-0

Using config file "./343-3-0-0".

Error: Failed to create device.

    stdout: 

    stderr: 

Check that target "/home/xenlabs/labs/cs343/hw3/group0/overflow.img" exists and that blktap2 driver installed in dom0.

And with 'tap:tapdisk:aio:', the system hung for almost a minute on the xm create command. Then it returned this error: 

# xm create 343-3-0-0

Using config file "./343-3-0-0".

Error: Device 768 (tap) could not be connected. Hotplug scripts not working.

Any insight? I was not able to get tap:aio to work on Debian Lenny Dom0 either, but I would really love to get it to work! 

On Wed, Mar 9, 2011 at 8:50 PM, John Weekes <lists.xen@xxxxxxxxxxxxxxxxxx> wrote:

On 3/9/2011 5:20 PM, Garrett Robinson wrote:

Success! I was able to boot my HVM sarge guest after making two changes.

The first repaired a simple mistake - I had partitioned a single disk image using the installer in qemu with a swap and an everything else partition. The "Domain not found" error went away as soon as I replaced the erroneous "hda1" with "hda" in the disk parameter.

Shoot, I missed that, too.

The second is more of a long-standing problem. In order to get the guest to boot, I need to completely disable networking by commenting out the vif=[] line. Trying to use networking, even with the defaults, results in the "xenbr0 not found" error seen earlier in /var/log/xen/qemu-dm-sarge.

That's one that I still don't quite get, but must have something to do with broken networking scripts.

Another question I have is this: had anybody had any luck using tap:aio on Xen4.0/Debian? Simply replacing "file:" with "tap:aio" did not work. I would love to take advantage of the efficiency of the aio driver, so any advice with regards to this would be appreciated!

Try "tap2:tapdisk:aio:" -- it should work, in 4.0.1. Failing that, try "tap:tapdisk:aio".

-John

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

--
Garrett Robinson
(484) 802-3882
Oberlin College '11

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