In my /var/log/xen folder I have a bunch of qemu log files, when I try to create my windows xp setup domain a new one is created with this output; domid: 10 qemu: the number of cpus is 1 qemu: could not open hard disk image ''sys_vg/windows_os'' /etc/xen/qemu-ifup: could not launch network script Could not initialize device ''tap'' Is this perhaps why my setup isn''t starting? Does anyone know what it means, I can''t really understand why the disk image isn''t loadable. Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
lists@higgers.me.uk
2006-Dec-10 20:59 UTC
[Xen-users] HVM DomU Under openSUSE 10.2 (hotplug scripts not working)
Hi All, I''ve just installed openSUSE 10.2 on my AMD X2 system but when I try to start an HVM domU I get the following error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. I''ve had this problem under openSUSE 10.1 and followed the steps under the network troubleshooting section: http://en.opensuse.org/Installing_Xen3 to fix the problem. However, these steps don''t seem to fix the problem in openSUSE 10.2. Has anyone got Xen working in openSUSE 10.2 or have any suggestions on what I should try? Many thanks in advance, Steve. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> In my /var/log/xen folder I have a bunch of qemu log files, when I try > to create my windows xp setup domain a new one is created with this output; > > domid: 10 > qemu: the number of cpus is 1 > qemu: could not open hard disk image ''sys_vg/windows_os''AFAIK you have to use full path to the disk device (including /dev) if you want to use an LVM volume as a disk for your HVM guest. That is, instead disk = [ ''phy:sys_vg/windows_os,ioemu:hda,w'' ] you should use disk = [ ''phy:/dev/sys_vg/windows_os,ioemu:hda,w'' ] Jirka -- `Funny, how just when you think life can''t possibly get any worse it suddenly does.'' -- Douglas Adams, "The Hitchhiker''s Guide to the Galaxy" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jiri, Thanks for your response, I figured it out eventually - I have windows installed and working... except for one thing, the network adapter does not install. This is because I have; vif = [ '' '' ] and what I should have is vif = [ ''type=ioemu'' ] - However, if I have this configuration the virtual machine doesn''t start, looking in the most recent qemu log reveals that the TAP device could not be created, I have TUN/TAP installed as a kernel module - has anyone seen this sort of problem before? Have any idea how to fix? Ryan. Jiri Denemark wrote:>> In my /var/log/xen folder I have a bunch of qemu log files, when I try >> to create my windows xp setup domain a new one is created with this output; >> >> domid: 10 >> qemu: the number of cpus is 1 >> qemu: could not open hard disk image ''sys_vg/windows_os'' >> > > AFAIK you have to use full path to the disk device (including /dev) if you > want to use an LVM volume as a disk for your HVM guest. That is, instead > > disk = [ ''phy:sys_vg/windows_os,ioemu:hda,w'' ] > > you should use > > disk = [ ''phy:/dev/sys_vg/windows_os,ioemu:hda,w'' ] > > > Jirka > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ulrich Windl
2006-Dec-11 07:47 UTC
Re: [Xen-users] HVM DomU Under openSUSE 10.2 (hotplug scripts not working)
On 10 Dec 2006 at 20:59, lists@higgers.me.uk wrote:> Hi All, > > I''ve just installed openSUSE 10.2 on my AMD X2 system but when I try to > start an > HVM domU I get the following error: > > Error: Device 0 (vif) could not be connected. Hotplug scripts not working.If everything is right from the ISO images, a bug report to https://bugzilla.novell.com/ would be the place to report. If you have files a report, or found the problem being there already, maybe post the bug number here. Regards, Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi.> vif = [ '' '' ] and what I should have is vif = [ ''type=ioemu'' ] - > However, if I have this configuration the virtual machine doesn''t start,Well, I have vif = [ ''type=ioemu, bridge=xenbr0'' ] which is the default taken from xmexample.hvm and everything works as expected.> looking in the most recent qemu log reveals that the TAP device could > not be created, I have TUN/TAP installed as a kernel moduleHmm, do you have that module loaded into the kernel (lsmod)? If not, try to insert it manually using modprobe. Perhaps, just autoloading doesn''t work for this module. I don''t have TUN/TAP as a module as I had to load it manually for OpenVPN... Jirka -- Living on Earth may be expensive, but it includes an annual free trip around the Sun. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Jiri! I do have the module loaded and I have a node /dev/net/tun so that side of things seems to be ok. If I manually try and create a tap adapter with ifconfig tap0 0.0.0.0 up then I still don''t get a tap device, I have to use tunctl to create a tap device before I can do this. So my thinking was, manually create a tap device with tunctl then start my guest VM. However what happens is the guest attempts to create a tap device with a number 1 higher than the one I''ve created, it doesn''t matter how many I try and make I get the same problem!!!!! Frustrating yes? Ryan. Jiri Denemark wrote:> Hi. > > >> vif = [ '' '' ] and what I should have is vif = [ ''type=ioemu'' ] - >> However, if I have this configuration the virtual machine doesn''t start, >> > Well, I have > > vif = [ ''type=ioemu, bridge=xenbr0'' ] > > which is the default taken from xmexample.hvm and everything works as > expected. > > >> looking in the most recent qemu log reveals that the TAP device could >> not be created, I have TUN/TAP installed as a kernel module >> > Hmm, do you have that module loaded into the kernel (lsmod)? If not, try to > insert it manually using modprobe. Perhaps, just autoloading doesn''t work for > this module. I don''t have TUN/TAP as a module as I had to load it manually for > OpenVPN... > > Jirka > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I have the same problem when I try to use a HVM domain with network-route or network-nat scripts (ie, when there''s no bridge created...) Para-virtualized domains work properly. François 2006/12/11, Ryan Worsley <R.C.Worsley@sussex.ac.uk>:> Hi Jiri! > > I do have the module loaded and I have a node /dev/net/tun so that side > of things seems to be ok. If I manually try and create a tap adapter > with ifconfig tap0 0.0.0.0 up then I still don''t get a tap device, I > have to use tunctl to create a tap device before I can do this. So my > thinking was, manually create a tap device with tunctl then start my > guest VM. However what happens is the guest attempts to create a tap > device with a number 1 higher than the one I''ve created, it doesn''t > matter how many I try and make I get the same problem!!!!! Frustrating yes? > > Ryan. > > Jiri Denemark wrote: > > Hi. > > > > > >> vif = [ '' '' ] and what I should have is vif = [ ''type=ioemu'' ] - > >> However, if I have this configuration the virtual machine doesn''t start, > >> > > Well, I have > > > > vif = [ ''type=ioemu, bridge=xenbr0'' ] > > > > which is the default taken from xmexample.hvm and everything works as > > expected. > > > > > >> looking in the most recent qemu log reveals that the TAP device could > >> not be created, I have TUN/TAP installed as a kernel module > >> > > Hmm, do you have that module loaded into the kernel (lsmod)? If not, try to > > insert it manually using modprobe. Perhaps, just autoloading doesn''t work for > > this module. I don''t have TUN/TAP as a module as I had to load it manually for > > OpenVPN... > > > > Jirka > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users