I had a similar problem, and my suggestion is what solved it, but that 
was with moonshine, and according to the documentation, the /dev/ shouldn't 
need to be specified.  I didn't look unto ioemu, as I've never used it and 
assumed it had to do with using a different method to emulate (input output 
emulation vs block device emulation) since either method would be not 
paravirtualised by virtue of the vm being and hvm.  However, all of that 
(regarding ioemu) is highly presumptious.  I seem to recall something about not 
being able to have four devices for some reason as well, though, so perhaps you 
should do some searching on that premise or try calling it hdc since you aren't 
using the cdrom at the same time.  I'm not a major linux player or anything, so 
I can't make heads or tails of the more detailed output you provided.  That 
said, my suggestions are shots in the dark.  Also, as an aside, I'm assuming -c 
works for you on other HVM configs, as the last time I tried it with an 
 HVM (probably FC6), I don't think it did.  Based on the error, though, I don't 
think the -c is your problem.  If it is, and assuming that you aren't putting 
the config file in an auto-start (at boot) location, the hvm config file can 
have a setting to start up a vnc window.
        Dustin

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield
Sent: Friday, January 18, 2008 09:09
To: [email protected]
Subject: Re: [Fedora-xen] xm create -c recovery fails

On Friday 18 January 2008 09:54:47 pm Dustin Henning wrote:
> Try this:
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> #      , ',hdc:cdrom,r'
>        , 'phy:/dev/hda,hdd,r'
>        ]
>
> Dustin

Same:
[EMAIL PROTECTED] ~]# time xm create -c recovery
Using config file "/etc/xen/recovery".
Error: Device 5696 (vbd) could not be connected. Hotplug scripts not working.

real    1m44.270s
user    0m0.085s
sys     0m0.046s
[EMAIL PROTECTED] ~]# cat /etc/xen/recovery | grep -Ev '^($|#)'
import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 128
name = "recovery"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
       , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
       , 'phy:/dev/hda,hdd,r'
       ]

etc
I don't believe /dev/hda has a different meaning from hda, and it seems that 
iomem (which I've not seen documented in this context) specifies "not 
paravirtualised" I/O. I got that from google when trying to solve the problem 
before posting to the list.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of John Summerfield Sent: Thursday, January 17, 2008 21:22
> To: [email protected]
> Subject: [Fedora-xen] xm create -c recovery fails
>
> I'm running F8, xen-3.1.2-1.fc8, 2.6.21.7-2890.fc9xen.
>
> I have a xen configuration which contains this stanza:
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
> #      , ',hdc:cdrom,r'
>        , 'phy:hda,ioemu:hdd,r'
>        ]
>
> If I comment out the line containing "'phy:hda,ioemu:hdd,r' then the xm
> create line works and the guest starts up and runs fine. Whether I have
> "ioemu" doesn't make any obvious difference, google suggested it.
>
> With the stanza as above, it fails:
> [EMAIL PROTECTED] ~]# time xm create -c recovery
> Using config file "/etc/xen/recovery".
> Error: Device 5696 (vbd) could not be connected. Hotplug scripts not
> working.
>
> real    1m44.750s
> user    0m0.080s
> sys     0m0.067s
> [EMAIL PROTECTED] ~]#
>
> The only other thing I see is the VNC console opens, but it displays with a
> white background.
>
> These are the messages logged to xend.log:
> [2008-01-18 11:00:24 2652] INFO (image:129) buildDomain os=hvm dom=27
> vcpus=1 [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice:
> vfb : {'vncunused': 1, 'other_config': {'vncunused':
> 1}, 'uuid': '6c9425f6-7800-4325-bcd7-b917ce2f8955'}
> [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vbd :
> {'uuid': '0f4b1edf-a164-6b3a-ebd2-395532720861', 'bootable':
> 1, 'driver': 'paravirtualised', 'dev': 'hda', 'uname':
> 'file:/var/lib/xen/images/recovery.img', 'mode': 'w'} [2008-01-18 11:00:24
> 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> '5c84f484-c9df-f60d-ccec-9a4bf7e47e64', 'bootable':
> 0, 'driver': 'paravirtualised', 'dev': 'hdb', 'uname':
> 'file:/var/lib/xen/images/WindowsXP.img', 'mode': 'w'} [2008-01-18 11:00:24
> 2652] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid':
> 'f34d1d46-dd15-7572-6661-26570af507a7', 'bootable':
> 0, 'driver': 'ioemu', 'dev': 'ioemu:hdd', 'uname': 'phy:hda', 'mode': 'r'}
> [2008-01-18 11:00:24 2652] INFO (XendDomainInfo:1458) createDevice: vif :
> {'bridge': 'xenbr0', 'mac': '00:16:3e:33:b1:83', 'type': 'ioemu', 'uuid':
> 'b5fca1da-8850-0723-bf2e-edbf7635832e'} [2008-01-18 11:00:24 2652] INFO
> (image:454) spawning device
> models: /usr/lib64/xen/bin/qemu-dm
> ['/usr/lib64/xen/bin/qemu-dm', '-d', '27', '-vcpus', '1', '-boot', 'cd',
> '-soundhw', 'sb16', '-localtime', '-serial', 'pty', '-acpi', '-usb',
> '-usbdevice', 'tablet', '-domain-name', 'recovery', '-net',
> 'nic,vlan=1,macaddr=00:16:3e:33:b1:83,model=rtl8139', '-net',
> 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.1:0', '-vncunused',
> '-vncviewer'] [2008-01-18 11:00:24 2652] INFO (image:458) device model pid:
> 29112
>
>
> "recovery" is a Debian system, I created it under KVM and I've mentioned it
> here before.
>
> Here is the Xen configuration:
> [EMAIL PROTECTED] xen]# cat /etc/xen/recovery | grep -Ev '^($|#)'
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 128
> name = "recovery"
> vif = [ 'type=ioemu, bridge=xenbr0' ]
> disk = [ 'file:/var/lib/xen/images/recovery.img,hda,w'
>        , 'file:/var/lib/xen/images/WindowsXP.img,hdb,w'
>        , 'phy:hda,ioemu:hdd,r'
>        ]
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> boot="cd"
> sdl=0
> vnc=1
> vncconsole=1
> vncpasswd=''
> stdvga=0
> serial='pty'
> soundhw='sb16'
> localtime=1
> usb=1
> usbdevice='tablet'
> [EMAIL PROTECTED] xen]#
>
> --
> Fedora-xen mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>
> --
> Fedora-xen mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/fedora-xen


--
Fedora-xen mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-xen



--
Fedora-xen mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-xen

Reply via email to