Re: [libvirt] Libvir on Hardy: file a bug or not?

2008-07-29 Thread Pau Garcia i Quiles
Quoting Mihamina Rakotomandimby (R12y)  
[EMAIL PROTECTED]:


I cannot help you with your problem but in case you want to try the  
latest and greatest libvirt, there are 0.4.4 packages available in my  
PPA: http://launchpad.net/~pgquiles/+archive (UNOFFICIAL AND  
UNSUPPORTED)



Hi,
I am using Ubuntu Hardy up to date.

When defining a domain with:
domain type='kvm' id='1'
  namexp/name
  uuiddd4618e5-1c48-a481-0671-d75f38f59037/uuid
  memory524288/memory
  currentMemory524288/currentMemory
  vcpu1/vcpu
  os
type arch='x86_64' machine='pc'hvm/type
boot dev='hd'/
  /os
  clock offset='localtime'/
  on_poweroffdestroy/on_poweroff
  on_rebootdestroy/on_reboot
  on_crashdestroy/on_crash
  devices
emulator/usr/bin/qemu-system-x86_64/emulator
disk type='file' device='cdrom'
  source file='/home/mihamina/xpjohnny.iso'/
  target dev='hdc' bus='ide'/
  readonly/
/disk
disk type='file' device='disk'
  source file='/home/mihamina/xp.img'/
  target dev='hda' bus='ide'/
/disk
interface type='bridge'
  mac address='00:16:3e:1e:b2:22'/
  source bridge='br0'/
  target dev='vnet1'/
/interface
input type='tablet' bus='usb'/
input type='mouse' bus='ps2'/
graphics type='vnc' port='5900' listen='127.0.0.1'/
  /devices
/domain

I get:

 virsh # start xp
 libvir: QEMU error : QEMU quit during console startup
 qemu: unknowm parameter 'boot' in
'file=/home/mihamina/xp.img,if=ide,boot=on'
 error: Failed to start domain xp

If I change the domain type with qemu, I have no error (and the
virtual machine starts without any problem.

This is my installed things:

$ dpkg -l | awk '/(virt|qemu|kvm)/{print $2,$3}'
kvm 1:62+dfsg-0ubuntu8
libvirt-bin 0.4.0-2ubuntu8
libvirt0 0.4.0-2ubuntu8
python-libvirt 0.4.0-2ubuntu8
python-virtinst 0.300.2-0ubuntu6
python-virtkey 0.50ubuntu0.1
qemu 0.9.1-1ubuntu1
virt-manager 0.5.3-0ubuntu10
virt-viewer 0.0.2-1ubuntu1

Is it an upstream bug or a distribution bug?
Who is supposed to be noticed? The packager or the upstream (where please)?

PS: I wrote because I saw
http://www.mail-archive.com/libvir-list@redhat.com/msg06109.html


--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list




--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [libvirt] VMware ESX

2008-05-20 Thread Pau Garcia i Quiles

Quoting Stefan de Konink [EMAIL PROTECTED]:


On Tue, 20 May 2008, Daniel Veillard wrote:


On Mon, May 19, 2008 at 02:28:10PM -0600, drew einhorn wrote:
 Hi,

  Hi,

 I have some code that can probably be hacked into a libvirt driver for
 VMware ESX.

  interesting, how did you go? I did some experimentation using SOAP and
gsoap2 a few weeks ago that i need to restart. Did you use VIX instead ?


I read about VIX again, but is this already working for ESX? On their site
and fora they mention Workstatation/Server only.


According to http://communities.vmware.com/thread/115071 the VIX API  
will be supported in ESX in the future.


--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [Libvir] PATCH: Support serial parallel devices in QEMU driver

2008-04-15 Thread Pau Garcia i Quiles

Quoting Daniel P. Berrange [EMAIL PROTECTED]:

Cool stuff. I've not read the patch because it's quite big but I've  
got a couple of questions:



 - Run a TCP  server and wait for clients to connect, using telnet
   protocol over wire:

serial type='tcp'
  source mode='bind' host='127.0.0.1' service='' wiremode='telnet'/
  target port='0'/
/serial

 - Run a TCP client connecting to a remote host to send data in
   raw format:

serial type='tcp'
  source mode='connect' host='127.0.0.1' service='' wiremode='raw'/
  target port='0'/
/serial


1) Is any of those two an implementation of RFC 2217? (Telnet Com  
Port Control Option)


2) Will all this serial port flavors be available for all drivers  
(qemu, kvm, xen, etc) or will they all be available for Xen, then only  
some for the other drivers?


Thank you.

--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [Libvir] modele1000/model - Specifying model in XML Configs

2008-04-08 Thread Pau Garcia i Quiles

Quoting Richard W.M. Jones [EMAIL PROTECTED]:


On Mon, Apr 07, 2008 at 10:51:56PM +0100, Henri Cook wrote:

I just tried to port a few customers over to this libvirt setup i'm
hoping to run and I couldn't get their machines started because there's
no mechanism to specify a model in the XML!

I know redhat have changed KVM's default driver to e1000, which I think
is the one I like the most and almost if not all of my VMs use. Ubuntu
haven't done that yet however!

Is there a model directive in the latest version? In the works? Just so
I know which solution I should pursue (updating libvirt or harassing
ubuntu to change the default)


There isn't a way to select the model, but there ought to be.  In KVM
64 the following NIC models are supported:

  i82551 i82557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio

Part of the problem with implementing this will be validating the
model (unless we just pass the model string directly to qemu which
could lead to errors).  The documentation suggests running qemu with
'-net nic,model=?' to list the models, and there is code in
qemu/hw/pci.c to implement this, but it just doesn't work for me.

  $ qemu-kvm -net nic,model=?

  [ prints full help because of the missing hda parameter ]

  $ qemu-kvm -net nic,model=? hda=/dev/null
  open /dev/kvm: Permission denied
  Could not initialize KVM, will disable KVM support
  Warning: vlan 0 is not connected to host network
  qemu: could not open disk image hda=/dev/null

  $ qemu-kvm -net nic,model=? hda=/dev/zero
  open /dev/kvm: Permission denied
  Could not initialize KVM, will disable KVM support
  Warning: vlan 0 is not connected to host network
  qemu: could not open disk image hda=/dev/zero

  $ touch /tmp/file
  $ qemu-kvm -net nic,model=? hda=/tmp/file
  open /dev/kvm: Permission denied
  Could not initialize KVM, will disable KVM support
  Warning: vlan 0 is not connected to host network
  qemu: could not open disk image hda=/tmp/file

  $ dd if=/dev/zero of=/tmp/file bs=1024 count=1024
  1024+0 records in
  1024+0 records out
  1048576 bytes (1.0 MB) copied, 0.00765395 s, 137 MB/s
  $ qemu-kvm -net nic,model=? hda=/tmp/file
  open /dev/kvm: Permission denied
  Could not initialize KVM, will disable KVM support
  Warning: vlan 0 is not connected to host network
  qemu: could not open disk image hda=/tmp/file


The same error happens in KVM and Qemu (not qemu-kvm) on Ubuntu. I'd  
say the problem belongs to Qemu, not to KVM.


--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [Libvir] [PATCH] Allow selection of the NIC model in QEMU/KVM

2008-04-08 Thread Pau Garcia i Quiles

Quoting Richard W.M. Jones [EMAIL PROTECTED]:


This patch allows selection of the NIC model for QEMU/KVM domains.
The selection is done by adding a model/ element to the XML, as in
this example:

interface type='user'
  mac address='00:16:3e:33:b8:d3'/
  model type='ne2k_pci'/
/interface

The model type string is only checked to make sure it's a short
alpha-numeric + underscore, since it seems impractical to extract the
actual list of supported models.


I've found how to get the list of supported models:

[EMAIL PROTECTED]:~$ kvm -net nic,model=? -hda ''
Warning: vlan 0 is not connected to host network
qemu: Supported ISA NICs: ne2k_isa
qemu: Supported PCI NICs: i82551 i82557b i82559er ne2k_pci pcnet  
rtl8139 e1000 virtio




If you choose a supported model then QEMU starts up with this extra
-nic parameter:

  /usr/bin/qemu-kvm -M pc -m 500 -smp 1 -monitor pty \
-boot c -hda /var/lib/xen/images/rhel51x32kvm.img \
-net nic,macaddr=00:16:3e:33:b8:d3,vlan=0,model=ne2k_pci -net   
user,vlan=0 \

-usb -vnc 127.0.0.1:0

If you choose a non-existant model then you get the error:

  libvir: QEMU error : internal error QEMU quit during monitor startup




--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [Libvir] error : could not connect to xen:///; error: failed to connect to the hypervisor

2008-03-26 Thread Pau Garcia i Quiles

Quoting Guido Günther [EMAIL PROTECTED]:


On Wed, Mar 26, 2008 at 02:23:05PM +, Richard W.M. Jones wrote:

Currently (libvirt 0.4.0-6) the logic is:

There's a 0.4.1 package in exprimental but the autobuilder didn't pick
it up yet so it's only available on ppc:
  http://packages.debian.org/experimental/libvirt-bin
I'll move that one around once 0.4.0 has been built on all
architectures:
  http://buildd.debian.org/~jeroen/status/package.php?p=libvirt


You can backport the package yourself:
1) download the .tar.gz, the .diff.gz and the .dsc
2) dpkg-source -x file.dsc
3) go into the dir
4) dpkg-buildpackage -rfakeroot

If dependency problems arise and you don't want to pollute your system  
installing those packages, replace step 4 with:

4a) debuild -S -sa
4b) sudo pbuilder build ../file.dsc

But you need to have installed pbuilder and have run pbuilder create  
before 4b (pbuilder is an UML environment which downloads all the  
dependencies, builds the packages and stores them usually in  
/var/cache/pbuilder/result )


--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [Libvir] Windows sizeof(long) != Linux sizeof(long)

2008-01-23 Thread Pau Garcia i Quiles

Quoting Richard W.M. Jones [EMAIL PROTECTED]:


Daniel P. Berrange wrote:

Just discovered that on x86_64,  Windows and Linux differ in what they
think sizeof(long) to be.

 http://lists.xensource.com/archives/html/xen-devel/2008-01/msg00736.html
 http://www.winehq.org/pipermail/wine-devel/2005-July/038602.html


Oh yes.  I haven't even tried Windows x86-64 (only 32 bit Windows).  I
don't think there is even a version of MinGW which is available for it.


Actually, there is. Unofficial and still experimental but it might be  
useful for testing and finding bugs:

http://sourceforge.net/projects/mingw-w64/
http://www.drangon.org/mingw/

--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list