The deployment files are mostly identical, apart from the fact that the 2.0 version uses the new "image" tag to specify the boot disk. The host machine is the same physical machine and the guest is the same image. I tried most network card models, including virtio, all with the same outcome.
There are two more differences I could find so far, but they both don't seem relevant to the network interface: * 2.0 uses a different home directory on the host compared to 1.4 * in the libvirt log file on the host: The 2.0 start-up command uses if=scsi, while the 1.4 command uses if=ide for the main boot disk. To help me debug this: Am I right to assume that the only thing that OpenNebula does on the host machine is executing the command which is logged in /var/log/libvirt/qemu/xx.log.l? or is there anything else that is done on the host when starting a virtual machine? I'll update to the 2.0 installation to the Release candidate and try changing the home directory and scsi to ide and see how it goes. Carsten -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ruben S. Montero Sent: Friday, 24 September 2010 17:22 To: Friedrich, Carsten (ICT Centre, Acton) Cc: [email protected] Subject: Re: [one-users] [ExternalEmail] Guest cannot configure network interface if started from OpenNebula Hi, This is strange as the code for KVM is the same, I'd expect this to be a Ubuntu 10.4 specific problem: 1.- Could you check if deployment.0 files (in $ONE_LOCATION/var/<vm_id>) are different for 1.4 and 2.0 2.- Are you using the same guest/host OS combination for 1.4 and 2.0? If not can you try to add virtio to your NICS, like NIC = [ NETWORK = "..." , model="virtio" ] Thanks for your feedback! Ruben On Fri, Sep 24, 2010 at 8:40 AM, <[email protected]> wrote: > Surprisingly this problem seems to be OpenNebula 2.0 specific. When I switch > back to my old 1.4 installation, the same image and template work fine... > > > > Carsten > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Friday, 24 September 2010 15:29 > To: [email protected] > Subject: [ExternalEmail] [one-users] Guest can configure network interface > if started from OpenNebula > > > > Hi, > > > > I'm looking for some ideas how to debug the following problem: > > > > * I use OpenNebula 2.0 beta. > > * I have a Ubuntu 10.4 guest image. > > * I have a Ubuntu 10.4 host with kvm and its network interface set up in > bridging mode. > > > > If I start the guest image from the "Virtual Machine Manager" application > the guest can see and configure its network interface without problems. If I > start the same guest image, with as similar parameters as possible, from > OpenNebula it boots fine and I can connect through VNC, but the guest cannot > configure its network card. It can see that the device exists and list it on > "ifconfig -a", but any attempt to bring it up or assign it an IP address > results in error messages. An ifconfig on the host reveals that vnet0 and > vnet1 were created and attached to the bridge. The ifconfig output is > basically identical (apart from MAC etc...). > > > > Any ideas on what the problem could be or what I should look at would be > highly appreciated. I'm happy to send more detailed information like xml > dump from virsh, ifconfig output etc. if this helps. > > > > Thanks, > > Carsten > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- Dr. Ruben Santiago Montero Associate Professor (Profesor Titular), Complutense University of Madrid URL: http://dsa-research.org/doku.php?id=people:ruben Weblog: http://blog.dsa-research.org/?author=7 _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
