| |
|
 |
|
 |
|
|
|
| |
|
|
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@xxxxxxxxxxxx>:
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home