- Users - libvirt List Archives

[libvirt-users] Live Block Migration with additional attached storage
by Chun-Hung Chen 07 Sep '12

07 Sep '12

Dear all, I am planning to use live block migration with one VM running on local disk and also attached additional disk from iSCSI or other shared storage. When block migration, not only local VM disk is copied to the destination but also the attached additional disk from shared storage. It is not desired in this situation. I just want the local VM disk is copied. Is there anyway to do this scenario? Does the concept of storage pool help this? I browse the source code but don't find hints right now. Thanks. Regards, Arnose

2 5

[libvirt-users] QEMU cmdline for default -smp reasonable (qemuBuildSmpArgs) ?
by sanjay 07 Sep '12

07 Sep '12

Hi! When only the vCPU tag is specified, libvirt by default generates a multi-socket topology(sockets=vCPUs,cores=1,threads=1) for the qemu command line. Is there a specific reason behind choice of this default behavior? Could a default of (socket=1,cores=vCPUs,threads=1) would have been a better choice ? -- Regards, Sanjay

2 1

[libvirt-users] defining directly to the wan/lan
by gary artim 07 Sep '12

07 Sep '12

I have a fedora system configured and running with virsh using kvm/qemu. All I want is to have a fixed ipaddress for that virtual machine. I know that there is the Host and Guest sides to the network. The host has virbr0 interface, which i guess is a bridge. Seem when ever I define a interface to the guest with a type=routed it hoses my other interfaces on the host and requires a console reboot -- completely hanging the network. I'm no networking expert, but there must be a simple N step procedure for defining a static IPaddress to route to a guest machine? Has anyone got this working and have a procedure. My network has 2 nic, eth0 and eth1 (10.0.0.253 and 10.0.1.253), one nic has a route to an nfs machine, the other passes through a linux based router to the wan. I can alias the 10.0.1.253 (eth0) to another address in the subnet, like 10.0.1.251 (eth0:0) and would like to use it in some way to connect to the guest -- I have the nat/routing working fine from the router to eth0:0. The network for libvirt is confusing. It not obvious which side (guest or host) your defining and seem to keep multiple definitions around, even after a restart of libvirtd.service. An help would be great!

1 0

[libvirt-users] problem defining ipaddress
by gary artim 07 Sep '12

07 Sep '12

I have a fedora system configured and running with virsh using kvm/qemu. All I want is to have a fixed ipaddress for that virtual machine. I know that there is the Host and Guest sides to the network. The host has virbr0 interface, which i guess is a bridge. Seem when ever I define a interface to the guest with a type=routed it hoses my other interfaces on the host and requires a console reboot -- completely hanging the network. I'm no networking expert, but there must be a simple N step procedure for defining a static IPaddress to route to a guest machine? Has anyone got this working and have a procedure. My network has 2 nic, eth0 and eth1 (10.0.0.253 and 10.0.1.253), one nic has a route to an nfs machine, the other passes through a linux based router to the wan. I can alias the 10.0.1.253 (eth0) to another address in the subnet, like 10.0.1.251 (eth0:0) and would like to use it in some way to connect to the guest -- I have the nat/routing working fine from the router to eth0:0. The network for libvirt is confusing. It not obvious which side (guest or host) your defining and seem to keep multiple definitions around, even after a restart of libvirtd.service. An help would be great! I have read all the libvirt web info and find it difficult to put the steps together...

1 0

[libvirt-users] Fwd: non-blocking virtConnectOpen
by lulin Fan 06 Sep '12

06 Sep '12

Hi I am writing a web-based management tool for KVM, it will manager a lot of remote KVM host, when user add a new connection from the UI, it will take a long time to open the libvirt connection sometimes due to the network problem, during this progress, the management tool will block the request of other user, it is not a good idea for users. BR Fan On 5 September 2012 14:55, Timon Wang <timonwst(a)gmail.com> wrote: > > > On Wed, Sep 5, 2012 at 11:53 AM, lulin Fan <fan.luliin(a)gmail.com> wrote: > > Hi all, > > > > does anybody know how to do non-blocking virtConnectOpen? does libvirt > > support it or not cause I can't find any document about it? or should I > need > > create a thread to do it? > > It's worth to use non-blocking? What will you do without connect? If it's > not related with libvirt connection, you can do in it in another thread if > you like. > > > > > > Thanks > > > > Fan > > > > _______________________________________________ > > libvirt-users mailing list > > libvirt-users(a)redhat.com > > https://www.redhat.com/mailman/listinfo/libvirt-users > > > > -- > Focus on: Server Vitualization, Network security,Scanner,NodeJS,JAVA,WWW > Blog: http://www.nohouse.net >

2 1

[libvirt-users] non-blocking virtConnectOpen
by lulin Fan 05 Sep '12

05 Sep '12

Hi all, does anybody know how to do non-blocking virtConnectOpen? does libvirt support it or not cause I can't find any document about it? or should I need create a thread to do it? Thanks Fan

3 2

[libvirt-users] virDomainMemoryPeek: bad behavior under workload
by NoxDaFox 05 Sep '12

05 Sep '12

Greetings, I am working on a platform for analysis automation. I need to run several Virtual Environments concurrently and record information about their behavior. I wrote some months ago about the capability of reading the Memory during the Environment's execution (in paused state). What do I need is the complete linear memory image, byte per byte, nothing special; I will give this output to tools and parsers like Volatility to get the value from it. I looked around and the only way to get the memory in such a way is using the QEMU monitor command `pmemsave`. I am using libvirt through its Python bindings and the virDomainQemuMonitorCommand seems not to be exposed by the API so, as suggested in some mails I read into the mailig list, I switched to virDomainMemoryPeek. Using this function keeps up to 14-16 seconds to read 512Mb of memory with the 64Kb limitation and 2-3 seconds with the 1Mb one; but the most annoying thing is that I can't run several environment concurrently as the function keeps failing. Here's the typical output: File "/home/nox/workspace/NOX/src/NOX/hooks.py", line 134, in trigger hook.trigger(event) File "/home/nox/workspace/NOX/src/NOX/hooks.py", line 33, in trigger self.handlers[event]() File "/home/nox/workspace/NOX/hooks/volatility.py", line 81, in memory_dump for block in Memory(self.ctx): File "/home/see/workspace/NOX/src/NOX/lib/libtools.py", line 179, in next libvirt.VIR_MEMORY_PHYSICAL) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1759, in memoryPeek ret = libvirtmod.virDomainMemoryPeek(self._o, start, size, flags) SystemError: error return without exception set I can't run more than 3 environments concurrently on a Xeon Quad with 8Gb of memory. I guess the RPC reply goes in timeout because the system is under heavy load but I'm not sure as the error output is quite obscure. Is there any solution to this issue? Is it possible to raise the RPC reply timeout value so that, even if slowly, I eventually get the memory dump? If through virsh I use the QEMU `pmemsave` command, I get the memory dump in less than one second; is there any way to obtain the same performance? Thanks anyway for making libvirt the great tool it is! NoxDaFox

2 4

[libvirt-users] Libvirt daemon segfaults when run as root
by Shawn Furrow 05 Sep '12

05 Sep '12

Hi all, For some reason when I run "libvirtd -d" as root it seems to not start. I investigate by running "libvirtd -v" as root and I get a segfault. Here is the output: 2012-08-23 19:01:23.237+0000: 27464: info : libvirt version: 0.10.0 > 2012-08-23 19:01:23.237+0000: 27464: error : virDriverLoadModule:78 : > failed to load module > /usr/local/lib/libvirt/connection-driver/libvirt_driver_qemu.so > /usr/local/lib/libvirt/connection-driver/libvirt_driver_qemu.so: undefined > symbol: virSecurityManagerGetProcessLabel > 2012-08-23 19:01:23.238+0000: 27464: error : virDriverLoadModule:78 : > failed to load module > /usr/local/lib/libvirt/connection-driver/libvirt_driver_lxc.so > /usr/local/lib/libvirt/connection-driver/libvirt_driver_lxc.so: undefined > symbol: virSecurityManagerGetProcessLabel > Caught Segmentation violation dumping internal log buffer: > > ====== start of log ===== > 2012-08-23 19:01:23.235+000027464: debug : main:1120 : Decided on pid file > path '/usr/local/var/run/libvirtd.pid' > 2012-08-23 19:01:23.235+000027464: debug : main:1130 : Decided on socket > paths '/usr/local/var/run/libvirt/libvirt-sock' and > '/usr/local/var/run/libvirt/libvirt-sock-ro' > 2012-08-23 19:01:23.235+000027464: debug : main:1168 : Ensuring run dir > '/usr/local/var/run/libvirt' exists > 2012-08-23 19:01:23.235+000027464: debug : virEventRegisterDefaultImpl:204 > : registering default event implementation > 2012-08-23 19:01:23.235+000027464: debug : virEventPollAddHandle:111 : > Used 0 handle slots, adding at least 10 more > 2012-08-23 19:01:23.235+000027464: debug : virEventPollInterruptLocked:697 > : Skip interrupt, 0 0 > 2012-08-23 19:01:23.236+000027464: debug : virEventPollAddHandle:136 : > EVENT_POLL_ADD_HANDLE: watch=1 fd=5 events=1 cb=0x7f323cd415a0 opaque=(nil) > ff=(nil) > 2012-08-23 19:01:23.236+000027464: debug : virEventRegisterImpl:177 : > addHandle=0x7f323cd423d0 updateHandle=0x7f323cd414a0 > removeHandle=0x7f323cd41360 addTimeout=0x7f323cd42220 > updateTimeout=0x7f323cd415e0 removeTimeout=0x7f323cd41260 > 2012-08-23 19:01:23.236+000027464: debug : virNetServerNew:407 : > srv=0xdd8890 refs=1 > 2012-08-23 19:01:23.236+000027464: debug : main:1206 : Dropping privileges > (if required) > 2012-08-23 19:01:23.236+000027464: debug : virDriverModuleInitialize:53 : > Module dir /usr/local/lib/libvirt/connection-driver > 2012-08-23 19:01:23.236+000027464: debug : virDriverLoadModule:66 : Module > load network > 2012-08-23 19:01:23.236+000027464: debug : virRegisterNetworkDriver:564 : > registering Network as network driver 4 > 2012-08-23 19:01:23.236+000027464: debug : virDriverLoadModule:66 : Module > load storage > 2012-08-23 19:01:23.236+000027464: debug : virRegisterStorageDriver:624 : > registering storage as storage driver 4 > 2012-08-23 19:01:23.236+000027464: debug : virDriverLoadModule:66 : Module > load secret > 2012-08-23 19:01:23.237+000027464: debug : virRegisterSecretDriver:684 : > registering secret as secret driver 3 > 2012-08-23 19:01:23.237+000027464: debug : virDriverLoadModule:66 : Module > load nwfilter > 2012-08-23 19:01:23.237+000027464: debug : virRegisterNWFilterDriver:714 : > registering nwfilter as network filter driver 3 > 2012-08-23 19:01:23.237+000027464: debug : virDriverLoadModule:66 : Module > load qemu > 2012-08-23 19:01:23.237+000027464: error : virDriverLoadModule:78 : failed > to load module > /usr/local/lib/libvirt/connection-driver/libvirt_driver_qemu.so > /usr/local/lib/libvirt/connection-driver/libvirt_driver_qemu.so: undefined > symbol: virSecurityManagerGetProcessLabel > 2012-08-23 19:01:23.238+000027464: debug : virDriverLoadModule:66 : Module > load lxc > 2012-08-23 19:01:23.238+000027464: error : virDriverLoadModule:78 : failed > to load module > /usr/local/lib/libvirt/connection-driver/libvirt_driver_lxc.so > /usr/local/lib/libvirt/connection-driver/libvirt_driver_lxc.so: undefined > symbol: virSecurityManagerGetProcessLabel > 2012-08-23 19:01:23.238+000027464: debug : virDriverLoadModule:66 : Module > load uml > 2012-08-23 19:01:23.238+000027464: debug : virRegisterDriver:732 : > driver=0x7f3232ec7760 name=UML > 2012-08-23 19:01:23.238+000027464: debug : virRegisterDriver:747 : > registering UML as driver 6 > 2012-08-23 19:01:23.238+000027464: debug : virDriverLoadModule:66 : Module > load xen > 2012-08-23 19:01:23.239+000027464: debug : virRegisterDriver:732 : > driver=0x7f3232caad00 name=Xen > 2012-08-23 19:01:23.239+000027464: debug : virRegisterDriver:747 : > registering Xen as driver 7 > 2012-08-23 19:01:23.239+000027464: debug : virNetServerProgramNew:63 : > prog=0xddca40 refs=1 > 2012-08-23 19:01:23.239+000027464: debug : virNetServerProgramRef:84 : > prog=0xddca40 refs=2 > 2012-08-23 19:01:23.239+000027464: debug : virNetServerProgramNew:63 : > prog=0xddcbc0 refs=1 > 2012-08-23 19:01:23.239+000027464: debug : virNetServerProgramRef:84 : > prog=0xddcbc0 refs=2 > 2012-08-23 19:01:23.239+000027464: debug : virEventPollInterruptLocked:697 > : Skip interrupt, 0 0 > 2012-08-23 19:01:23.239+000027464: debug : virEventPollAddHandle:136 : > EVENT_POLL_ADD_HANDLE: watch=2 fd=7 events=1 cb=0x7f323ce241e0 > opaque=0xdd8890 ff=(nil) > 2012-08-23 19:01:23.239+000027464: debug : main:1257 : Attempting to > configure auditing subsystem > 2012-08-23 19:01:23.239+000027464: debug : main:1263 : Proceeding without > auditing > 2012-08-23 19:01:23.239+000027464: debug : virHookCheck:119 : No hook > script /usr/local/etc/libvirt/hooks/daemon > 2012-08-23 19:01:23.239+000027464: debug : virHookCheck:119 : No hook > script /usr/local/etc/libvirt/hooks/qemu > 2012-08-23 19:01:23.239+000027464: debug : virHookCheck:119 : No hook > script /usr/local/etc/libvirt/hooks/lxc > 2012-08-23 19:01:23.239+000027464: debug : daemonSetupNetworking:464 : > Registering unix socket /usr/local/var/run/libvirt/libvirt-sock > 2012-08-23 19:01:23.239+000027464: debug : virNetSocketNew:119 : > localAddr=0x7fff419bf530 remoteAddr=(nil) fd=9 errfd=-1 pid=0 > 2012-08-23 19:01:23.239+000027464: debug : virNetSocketNew:179 : > RPC_SOCKET_NEW: sock=0xddcbf0 refs=1 fd=9 errfd=-1 pid=0 > localAddr=127.0.0.1;0, remoteAddr=(null) > 2012-08-23 19:01:23.239+000027464: debug : virNetSocketRef:713 : > RPC_SOCKET_REF: sock=0xddcbf0 refs=2 > 2012-08-23 19:01:23.239+000027464: debug : virEventPollInterruptLocked:697 > : Skip interrupt, 0 0 > 2012-08-23 19:01:23.239+000027464: debug : virEventPollAddHandle:136 : > EVENT_POLL_ADD_HANDLE: watch=3 fd=9 events=0 cb=0x7f323ce2ab10 > opaque=0xddcbf0 ff=0x7f323ce2ba60 > 2012-08-23 19:01:23.239+000027464: debug : daemonSetupNetworking:474 : > Registering unix socket /usr/local/var/run/libvirt/libvirt-sock-ro > 2012-08-23 19:01:23.239+000027464: debug : virNetSocketNew:119 : > localAddr=0x7fff419bf530 remoteAddr=(nil) fd=10 errfd=-1 pid=0 > 2012-08-23 19:01:23.239+000027464: debug : virNetSocketNew:179 : > RPC_SOCKET_NEW: sock=0xddd430 refs=1 fd=10 errfd=-1 pid=0 > localAddr=127.0.0.1;0, remoteAddr=(null) > 2012-08-23 19:01:23.239+000027464: debug : virNetSocketRef:713 : > RPC_SOCKET_REF: sock=0xddd430 refs=2 > 2012-08-23 19:01:23.239+000027464: debug : virEventPollInterruptLocked:697 > : Skip interrupt, 0 0 > 2012-08-23 19:01:23.239+000027464: debug : virEventPollAddHandle:136 : > EVENT_POLL_ADD_HANDLE: watch=4 fd=10 events=0 cb=0x7f323ce2ab10 > opaque=0xddd430 ff=0x7f323ce2ba60 > 2012-08-23 19:01:23.239+000027464: debug : virNetServerRef:420 : > srv=0xdd8890 refs=2 > 2012-08-23 19:01:23.239+000027464: debug : virNetlinkEventServiceStart:656 > : libnl was not available at build time > 2012-08-23 19:01:23.239+000027464: debug : virNetServerRun:714 : > srv=0xdd8890 quit=0 > 2012-08-23 19:01:23.239+000027464: debug : virEventRunDefaultImpl:244 : > running default event implementation > 2012-08-23 19:01:23.239+000027464: debug : virEventPollCleanupTimeouts:501 > : Cleanup 0 > 2012-08-23 19:01:23.239+000027464: debug : virEventPollCleanupTimeouts:537 > : Found 0 out of 0 timeout slots used, releasing 0 > 2012-08-23 19:01:23.239+000027464: debug : virEventPollCleanupHandles:549 > : Cleanup 4 > 2012-08-23 19:01:23.240+000027464: debug : virEventPollMakePollFDs:378 : > Prepare n=0 w=1, f=5 e=1 d=0 > 2012-08-23 19:01:23.240+000027475: debug : virStateInitialize:798 : > Running global init for Remote state driver > 2012-08-23 19:01:23.240+000027475: debug : virStateInitialize:798 : > Running global init for Network state driver > 2012-08-23 19:01:23.240+000027464: debug : virEventPollMakePollFDs:378 : > Prepare n=1 w=2, f=7 e=1 d=0 > 2012-08-23 19:01:23.240+000027464: debug : virEventPollMakePollFDs:378 : > Prepare n=2 w=3, f=9 e=0 d=0 > 2012-08-23 19:01:23.240+000027464: debug : virEventPollMakePollFDs:378 : > Prepare n=3 w=4, f=10 e=0 d=0 > 2012-08-23 19:01:23.240+000027464: debug : > virEventPollCalculateTimeout:320 : Calculate expiry of 0 timers > 2012-08-23 19:01:23.240+000027464: debug : > virEventPollCalculateTimeout:346 : Timeout at 0 due in -1 ms > 2012-08-23 19:01:23.240+000027464: debug : virEventPollRunOnce:614 : > EVENT_POLL_RUN: nhandles=2 timeout=-1 > > ====== end of log ===== > Segmentation fault/ However, when I run "libvirtd -d" as me, it does not segfault and continues running. However I cannot connect to the libvirt-sock because it gets created at "$HOME/.cache/libvirt/libvirt-sock" but virsh looks for it at "/usr/local/var/run/libvirt-sock". Here is what I get when I run "libvirtd -v" as me: 2012-08-23 19:02:15.145+0000: 27483: info : libvirt version: 0.10.0 > 2012-08-23 19:02:15.145+0000: 27483: error : virDriverLoadModule:78 : > failed to load module > /usr/local/lib/libvirt/connection-driver/libvirt_driver_qemu.so > /usr/local/lib/libvirt/connection-driver/libvirt_driver_qemu.so: undefined > symbol: virSecurityManagerGetProcessLabel > 2012-08-23 19:02:15.145+0000: 27483: error : virDriverLoadModule:78 : > failed to load module > /usr/local/lib/libvirt/connection-driver/libvirt_driver_lxc.so > /usr/local/lib/libvirt/connection-driver/libvirt_driver_lxc.so: undefined > symbol: virSecurityManagerGetProcessLabel Any ideas why this is happening? I am on Ubuntu 10.04 running libvirt 0.10.0 with qemu-kvm 1.1 Thanks, Shawn -- Virginia Tech Bradley Department of Electrical and Computer Engineering B.S. Electrical Engineering B.S. Computer Engineering

2 1

Re: [libvirt-users] about open vswitch supporting？
by yue wang 04 Sep '12

04 Sep '12

On Tue, Sep 4, 2012 at 2:20 PM, yue wang <heuye.wang(a)gmail.com> wrote: > it seems the 'generic ethernet connection' network doesn't have the > 'virtualport ' element, so there is no way to associate it with an > interface's uuid. > are there any workaround？ > > > On Mon, Sep 3, 2012 at 6:41 PM, yue wang <heuye.wang(a)gmail.com> wrote: > >> Hi: >> >> i used to use linux bridge and specify interfaces by 'Generic ethernet connection' >> mode,after reading this page： >> http://libvirt.org/formatdomain.html#elementsNICS >> i am not sure if i need to change to another mode(eg:'virtual network') to >> specify interfaces when switching linux bridge to open vswitch? >> any suggestions? >> >> >> thanks! >> heuye >> > >

1 0

[libvirt-users] virtual network bug?
by Gene Czarcinski 04 Sep '12

04 Sep '12

I have had a number of occasions lately where a virtual "NAT" network (such as default) has stopped working. I have attempted to stop and then restart the network from the "network details" but the only thing that seems to work is to restart all of the virtual guests which use that network. I don't believe that I should have to do that. Is there some command which will "fix" things? I have had this happen to me a number of times but I am currently uncertain of the cause. Anyone know what is going on? I am not going to bugzilla this until. I do know one way to cause the problem. Disable the network in a virtual machine. Then using virt-manager's connection details menu, stop that (default) network ... then start it up again. Everything sort-of looks ok but it is not. Go back to the virtual machine and re-enable the previously disable network. Nope ... cannot connect. Start another virtual machine which uses that network and it works fine. In the "real world", I can disable a network, then remove a cable, connect the cable back up, re-enable the network and everything works. BTW, NetworkManager is used in all cases. Any ideas? Gene

2 2

[libvirt-users] error: Failed to start pool (already mounted)
by Ragnar Skúlason 04 Sep '12

04 Sep '12

Hi everyone, I have storage-pool that for some reason became inactive (possibly due to an error with pool-refresh in an old version of a Java API binding). I want to restart the pool but am unable to, due to the volume being mounted: # virsh pool-start [uuid] error: Failed to start pool [uuid] error: Requested operation is not valid: Target '/mnt/[uuid]' is already mounted We have tested this with versions 0.9.12 and 0.9.13. Is it possible to bypass this mount check and start the storage pool (forcefully)? Many thanks, Ragnar Skúlason

1 0

[libvirt-users] Fwd: vm pxe fail
by Alex Jia 01 Sep '12

01 Sep '12

----- Forwarded Message ----- From: "Alex Jia" <ajia(a)redhat.com> To: "Andrew Holway" <a.holway(a)syseleven.de> Cc: kvm(a)vger.kernel.org Sent: Friday, August 31, 2012 10:37:23 PM Subject: Re: [libvirt-users] vm pxe fail Hi Andrew, Great, BTW, in fact, you may pxe boot via VF of Intel82576, however, Intel82576 SR-IOV network adapters don't provide a ROM BIOS for the cards virtual functions (VF), but an image of such a ROM is available, and with this ROM visible to the guest, it can PXE boot. In libvirt's xml, you need to configure guest XML like this: <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address bus='XX' slot='XX' function='XX'/> </source> <boot order='1'/> <rom bar='on' file='/xxxx/ipxe-808610ca.rom'/> </hostdev> You need to build a ipxe-808610ca.rom by yourself, if you're interested in this, please refer to http://ipxe.org/. -- Regards, Alex ----- Original Message ----- From: "Andrew Holway" <a.holway(a)syseleven.de> To: "Alex Jia" <ajia(a)redhat.com> Cc: kvm(a)vger.kernel.org Sent: Friday, August 31, 2012 9:32:24 PM Subject: Re: [libvirt-users] vm pxe fail Hi, In the end the problem was SR-IOV enabled on the cards. I turned this off and everything worked ok. Im using HP 10G cards which are rebranded emulex. 0a:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) Thanks, Andrew On Aug 17, 2012, at 4:34 AM, Alex Jia wrote: > Hi Andrew, > I can't confirm a root reason based on your information, perhaps you may > try to find a reason by yourself via the following docs: > > http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed (Troubleshooting) > http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sec… (User Guide) > > If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your > network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks. > > -- > Regards, > Alex > > > ----- Original Message ----- > From: "Andrew Holway" <a.holway(a)syseleven.de> > To: kvm(a)vger.kernel.org > Sent: Thursday, August 16, 2012 8:25:35 PM > Subject: [libvirt-users] vm pxe fail > > Hallo > > I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips. on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump. > > Ive tried using various virtual interfaces. > > I can pxe boot my physical hosts with no problems. > > I can tftp fine from the physical host and see the traffic with ethdump > > Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12… > > Thanks, > > Andrew > > [root@node002 ~]# yum list | grep qemu > gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base > qemu-img.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates > qemu-kvm.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates > qemu-guest-agent.x86_64 2:0.12.1.2-2.295.el6_3.1 updates > qemu-kvm-tools.x86_64 2:0.12.1.2-2.295.el6_3.1 updates > > [root@node002 ~]# ethtool eth0 > Settings for eth0: > Supported ports: [ TP ] > Supported link modes: 10000baseT/Full > Supports auto-negotiation: No > Advertised link modes: 10000baseT/Full > Advertised pause frame use: No > Advertised auto-negotiation: No > Speed: Unknown! > Duplex: Unknown! (255) > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: off > MDI-X: Unknown > Supports Wake-on: g > Wake-on: g > Current message level: 0x00000014 (20) > Link detected: no > > [root@node002 ~]# brctl show > bridge name bridge id STP enabled interfaces > br0 8000.009c02241ae0 no eth1 > vnet0 > virbr0 8000.525400a6d5aa yes virbr0-nic > > [root@node002 ~]# ethtool vnet0 > Settings for vnet0: > Supported ports: [ ] > Supported link modes: > Supports auto-negotiation: No > Advertised link modes: Not reported > Advertised pause frame use: No > Advertised auto-negotiation: No > Speed: 10Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: off > MDI-X: Unknown > Current message level: 0xffffffa1 (-95) > Link detected: yes > > <domain type='kvm'> > <name>vm004</name> > <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid> > <memory unit='KiB'>2097152</memory> > <currentMemory unit='KiB'>2097152</currentMemory> > <vcpu placement='static'>2</vcpu> > <os> > <type arch='x86_64' machine='rhel6.3.0'>hvm</type> > <boot dev='hd'/> > </os> > <features> > <acpi/> > <apic/> > <pae/> > </features> > <clock offset='utc'/> > <on_poweroff>destroy</on_poweroff> > <on_reboot>restart</on_reboot> > <on_crash>restart</on_crash> > <devices> > <emulator>/usr/libexec/qemu-kvm</emulator> > <disk type='file' device='disk'> > <driver name='qemu' type='raw' cache='none'/> > <source file='/cm/shared/vm/vm004.img'/> > <target dev='hda' bus='ide'/> > <address type='drive' controller='0' bus='0' target='0' unit='0'/> > </disk> > <disk type='block' device='cdrom'> > <driver name='qemu' type='raw'/> > <target dev='hdc' bus='ide'/> > <readonly/> > <address type='drive' controller='0' bus='1' target='0' unit='0'/> > </disk> > <controller type='usb' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> > </controller> > <controller type='ide' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> > </controller> > <interface type='bridge'> > <mac address='00:00:00:00:00:0d'/> > <source bridge='br0'/> > <model type='rtl8139'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > </interface> > <serial type='pty'> > <target port='0'/> > </serial> > <console type='pty'> > <target type='serial' port='0'/> > </console> > <input type='mouse' bus='ps2'/> > <graphics type='vnc' port='-1' autoport='yes'/> > <video> > <model type='cirrus' vram='9216' heads='1'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> > </video> > <memballoon model='virtio'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> > </memballoon> > </devices> > </domain> > > > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users

1 0

[libvirt-users] whether before create a pool use type logical must create a vg or not?
by zhijun liu 30 Aug '12

30 Aug '12

whether before create a pool (use type logical) must create a vg or not? when I create pool named vg-test,but always occurs: error: Failed to create pool from pool.xml error: internal error Child process (/sbin/vgchange -ay vg-test) status unexpected: exit status 5

1 0

[libvirt-users] Running VirtualBox headless
by Dmitry Mikhin 30 Aug '12

30 Aug '12

Hello everyone, I'm trying to run a VirtualBox-based VM in headless mode, but apparently running out of luck. So far: - Fedora 14 host - libvirt 0.9.8 manually built from libvirt-0.9.8-1.fc14.src.rpm (later tested with 0.10.0 built from libvirt-0.10.0-1.fc17.src.rpm to the same effect) - I have a VBox 4.1.20 installed with extension pack - a virtual Windows XP guest - can start this machine from VirtualBox GUI - can start from "virsh -c vbox:///session start" - VRDP enabled in VirtualBox GUI The relevant entries in "virsh dumpxml" output are: <graphics type='desktop' display=':0.0'/> <graphics type='rdp' port='3388' multiUser='yes'/> - can connect to the running XP from rdesktop - can start the same machine using VBoxHeadless and connect from rdesktop - can start from virsh and connect from rdesktop All the above can be performed as a "su - otheruser", where otheruser has been added to vboxusers group, AND with access to X display (of the main, logged user) enabled by "xauth add ..." However, when no xauth access is enabled, "virsh start" fails: $ virsh --connect vbox:///session start vbox-windows-xp-32 error: Failed to start domain vbox-windows-xp-32 error: An error occurred, but the cause is unknown And I cannot remove the desktop graphics from the xml (edit as shown below, in vi remove the <graphics type='desktop'...> line, save, quit): $ virsh --connect vbox:///session edit vbox-windows-xp-32 error: internal error could not define a domain, rc=80bb0004 I set export VIRSH_DEBUG=0 export VIRSH_LOG_FILE="virsh.log" export LIBVIRT_DEBUG=1 export LIBVIRT_LOG_OUTPUTS="1:file:libvirt.log" and collected two log-files (tarball attached; this has been done using the older libvirt 0.9.8; upgrade to 0.10.0 did not solve the issue). Also, related or not, "virsh dumpxml" produces an xml file that is rejected by virt-xml-validate (with or without the graphics line): $ virsh --connect vbox:///session dumpxml vbox-windows-xp-32 > vbox-windows-xp-32.xml $ virt-xml-validate vbox-windows-xp-32.xml Relax-NG validity error : Extra element devices in interleave vbox-windows-xp-32.xml:20: element devices: Relax-NG validity error : Element domain failed to validate content vbox-windows-xp-32.xml fails to validate When the second user is allowed access to my display: $ xhost +SI:localuser:buildmaster all starts to work (and the Windows XP window pops up on my display whenever it wants). Any ideas how to make it work on the background? Many thanks for the wonderful and very useful library, Dmitry

1 0

[libvirt-users] network settings for an isolated network
by Christian Schmidt 30 Aug '12

30 Aug '12

Hi, I try to configure a kvm with a NIC, but no attached network to this NIC. I tried following methods: 1. Create a generic ethernet connection I configured the VM with following interface section: <interface type='ethernet'> <script path='/root/noscript.sh'/> <target dev='myvm_nic0'/> <interface/> The script /root/noscript.sh exists and is executable and has only an exit 0 statement. When I try to start the VM, virsh aborts with following error: error: Failed to start domain myvm error: internal error process exited while connecting to monitor: qemu-kvm: -netdev tap,script=/root/noscript.sh,id=hostnet1: could not configure /dev/net/tun (tap%d): Operation not permitted qemu-kvm: -netdev tap,script=/root/noscript.sh,id=hostnet1: Device 'tap' could not be initialized The tun module is loaded and I can create tap devices with tunctl. So there might be no problem... 2. I configurerd a network with no forward element. I've defined and started following network on the host with virsh net-define / net-start <network> <name>myvm_isolated</name> <bridge name='virbr_myvm_1' /> </network> The documentation says: "If there is no forward element, the network will be isolated from any other network (unless a guest connected to that network is acting as a router, of course)." The interface configuration of the domain was this: <interface type='network'> <mac address='00:12:67:bb:bb:11'/> <source network='myvm_isolated'/> <model type='e1000'/> </interface> The VM starts as expected. But the interface is connected to an host bridge like a NAT interface. There is a DHCP server in the network and the VM gets an IP Address and can ping and ssh to the VM-Server... I used following version of libvirt and qemu on SuSE Enterprise Linux Server SP2: # virsh version Compiled against library: libvir 0.9.6 Using library: libvir 0.9.6 Using API: QEMU 0.9.6 Running hypervisor: QEMU 0.15.1 Can you please tell me how to configure a not connected (isolated) network interface card for my VM? Regards, Christian

1 0

[libvirt-users] Use virsh command domjobinfo but get nothing
by Li, Chun Wen 29 Aug '12

29 Aug '12

Hi, all I test virsh comand "domjobinfo" on x86-i386 and PPC64 host. But Both get nothing. # virsh version Compiled against library: libvir 0.9.13 Using library: libvir 0.9.13 Using API: QEMU 0.9.13 Running hypervisor: QEMU 1.1.50 # virsh list Id Name State ---------------------------------------------------- 21 f16-ppc-qcow2 running 22 f16-blkiotune running 23 f16-device-attach running # virsh domjobinfo 21 Job type: None But I have run two jobs on domain 21 [root@localhost ~]# jobs [1]- Stopped top [2]+ Stopped vi install.log I searched the domjobinfo patch gave by Daniel P. Berrange, he said " This series introduces 2 new APIs to allow long running jobs to be monitored and cancelled. " Dose domjobinfo only monitor some special jobs in guest? Or does I miss something? Thanks & Regards Kimi Li

2 2

[libvirt-users] delete storage pool error
by zhijun liu 29 Aug '12

29 Aug '12

hi,all I create pool with lvm,but i carelessly add a blank space in the pool name like ' lvm_pool' , now I want to delete this pool,but encounter a error: error: Failed to delete pool lvm_pool error: internal error Child process (/sbin/vgremove -f lvm_pool) status unexpected: exit status 5 how to solve this problem? thanks

2 1

[libvirt-users] virsh reboot problem
by Andreas Davour 28 Aug '12

28 Aug '12

I am trying to reboot my virtual machines, running virsh reboot. Then I get the following error: error: this function is not supported by the connection driver: virDomainReboot Searching around I get the impression this should be fixed by now, since the bugs I find are old and resolved. These are the versions I'm running. Linux 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux libvirt-0.8.7-18.el6.x86_64 qemu-kvm-0.12.1.2-2.160.el6.x86_64 I also have acpid in both the host and the guest. Am I missing something? Thanks. /andreas

3 3

[libvirt-users] Why a max mem setting?
by Andreas Davour 28 Aug '12

28 Aug '12

Hi I have just started to investigate the possibilities of resizing memory for my kvm virtual machines on the fly. It works just fine with virsh setmem and that's great. Now, what I'm wondering about is the <memory> directive in the xml domain definition. Why would I not just set that to the size of available RAM in the host machine? Am I missing some nuance or finesse to the handling of memory? What would happen if I had three virtual machines with max set to physical max and then used setmem to give one of the virtual machines more than its third? Thank for any feedback. I could maybe just try the latter out, but I have no machine I could crash if that's the result... /andreas

2 1

[libvirt-users] What's the api virConnectBaselineCPU used for?
by Timon Wang 28 Aug '12

28 Aug '12

Could anyone tell me what is virConnectBaselineCPU exactly do. What could I do which this API. It's very nice to give me a simple example. -- Focus on: Network security,Scanner,NodeJS,JAVA,WWW Blog: http://www.nohouse.net

2 1

[libvirt-users] question about using openAuth with Python
by lulin Fan 27 Aug '12

27 Aug '12

Hi guys Is anybody can help me how to use openAuth to connect a remote URI without input the boring password? we assume the password of root for remote machine is "123456". Even I running the example in libvirt library esxlist.py(change uri to a qemu type and assign the username and password). Bellow is my simple test code, unfortunately it still need me to input the password. import libvirt def authcb(ncred, cbdata): for cred in ncred: if cred[0] == libvirt.VIR_CRED_AUTHNAME: cred[4] = "root" elif cred == libvirt.VIR_CRED_PASSPHRASE: cred[4] = "123456" return 0 class connection: def __init__(self, uri): self.uri = uri def open(self): auth = [[libvirt.VIR_CRED_AUTHNAME, libvirt.VIR_CRED_PASSPHRASE], authcb, None] vm_conn = libvirt.openAuth(self.uri, auth, 0); print self.uri if vm_conn == None: print 'Failed to open connection to %s' % self.uri for name in vm_conn.listDefinedDomains(): print name vm = vm_conn.lookupByName(name) if __name__ == '__main__': conn = connection('qemu+ssh://root@192.168.1.203/system') conn.open() Thanks fan

2 1

Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage.
by Rajesh Kumar Mallah 27 Aug '12

27 Aug '12

Dear Alex , What do you have in the Host ? Does the guests behave as we are expecting them to behave in our setup ? <offtopic> can i get rhel6.2 for trying? </offtopic> Also i have attached the files this time. Regards, Rajesh Kumar Mallah Tel. 91-11-46710500 (Ext:303) Cell +919811255597 Website: http://www.tradeindia.com/ \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | start planting | | | ----- "Alex Jia" <ajia(a)redhat.com> wrote: | From: "Alex Jia" <ajia(a)redhat.com> | To: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | Cc: libvirt-users(a)redhat.com, "vikas pandey" <vikas_pandey(a)tradeindia.com> | Sent: Monday, August 27, 2012 12:55:14 PM | Subject: Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage. | | Hi Rajesh, | I guess you forgot to attach your attachments in here. | As usual, I tried to directly assign a PF or VF of the Intel82576 | to guest on RHEL6.2, my box is Dell Optiplex 755. | | -- | Regards, | Alex | | | ----- Original Message ----- | From: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | To: "Alex Jia" <ajia(a)redhat.com> | Cc: libvirt-users(a)redhat.com, "vikas pandey" | <vikas_pandey(a)tradeindia.com> | Sent: Saturday, August 25, 2012 2:31:20 PM | Subject: Re: [libvirt-users] automatically detaching PCI host devices | from guest for SRIOV usage. | | Dear Alex/List , | | I am attaching a zip file that contains a set of files. | The files that start with case-1 is the case when the PCI | device is detached prior to shutdown. case-2 is otherwise. | | Kindly have a look when you have time and see if there | is any hints. | | BTW can you suggest in what free platform does SRIOV and direct | PCI assignment *really* works so that we could try on that as well. | | Regards, | Rajesh Kumar Mallah | Tel. 91-11-46710500 (Ext:303) | Cell +919811255597 | Website: http://www.tradeindia.com/ | \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | | start planting | | | | | | ----- "Alex Jia" <ajia(a)redhat.com> wrote: | | | From: "Alex Jia" <ajia(a)redhat.com> | | To: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | | Cc: libvirt-users(a)redhat.com, "vikas pandey" | <vikas_pandey(a)tradeindia.com> | | Sent: Thursday, August 23, 2012 8:21:58 AM | | Subject: Re: [libvirt-users] automatically detaching PCI host | devices from guest for SRIOV usage. | | | | ----- Original Message ----- | | From: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | | To: "Alex Jia" <ajia(a)redhat.com> | | Cc: libvirt-users(a)redhat.com, "vikas pandey" | | <vikas_pandey(a)tradeindia.com> | | Sent: Wednesday, August 22, 2012 7:37:05 PM | | Subject: Re: [libvirt-users] automatically detaching PCI host | devices | | from guest for SRIOV usage. | | | | | | | | | | | Could you attach your libvirtd.log? which's version your | libvirt? | | | in addition, if your guest has a desktop, please login and check | if | | | | | the network configuration exists issues. | | | | | | Thanks, | | | Alex | | | | Dear Alex , | | | | What logging level is useful for you ? | | | | Dear Rajesh, | | | | Level 1 (Debug) should be enough, but I guess it probably hasn't | more | | help for us, | | you had better to login the guest then check network when you were | | meeting this issue | | again, for example, to check if network configuration is valid and | try | | to restart | | relevant network services to see if the guest network can work | again | | or something | | like that, In addition, you shut down the guest via running 'halt' | in | | the guest, | | Does it work for you if you use libvirt relevant interface such as | | 'virsh shutdown guest' | | or 'virsh destroy guest'? | | | | | | Regards, | | Alex | | | | | | | | Regards, | | Rajesh Kumar Mallah | | Tel. 91-11-46710500 (Ext:303) | | Cell +919811255597 | | Website: http://www.tradeindia.com/ | | \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | | | start planting | | |

2 2

Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage.
by Rajesh Kumar Mallah 27 Aug '12

27 Aug '12

Dear Alex / List , I did some changes which i want you to know. I installed ixgbevf on the host and libvirt does attach and detach the VFs from the host and guests. But the connectivity issue is there. root@debian-squeeze:~# readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/ixgbevf root@debian-squeeze:~# /usr/local/libvirt/bin/virsh start new-installed Domain new-installed started root@debian-squeeze:~# readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub root@debian-squeeze:~# ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. >From 192.168.100.6 icmp_seq=1 Destination Host Unreachable >From 192.168.100.6 icmp_seq=2 Destination Host Unreachable >From 192.168.100.6 icmp_seq=3 Destination Host Unreachable >From 192.168.100.6 icmp_seq=4 Destination Host Unreachable >From 192.168.100.6 icmp_seq=5 Destination Host Unreachable >From 192.168.100.6 icmp_seq=6 Destination Host Unreachable >From 192.168.100.6 icmp_seq=7 Destination Host Unreachable >From 192.168.100.6 icmp_seq=8 Destination Host Unreachable >From 192.168.100.6 icmp_seq=9 Destination Host Unreachable 64 bytes from 192.168.101.10: icmp_req=10 ttl=64 time=812 ms 64 bytes from 192.168.101.10: icmp_req=11 ttl=64 time=0.351 ms 64 bytes from 192.168.101.10: icmp_req=12 ttl=64 time=0.293 ms 64 bytes from 192.168.101.10: icmp_req=13 ttl=64 time=0.364 ms ^C root@debian-squeeze:~# ssh 192.168.101.10 root(a)192.168.101.10's password: root@new-installed:~# halt The system is going down for system halt NOW!s/0) (Tue Aug 21 18:28:27 2012): root@new-installed:~# Connection to 192.168.101.10 closed by remote host. Connection to 192.168.101.10 closed. root@debian-squeeze:~# root@debian-squeeze:~# root@debian-squeeze:~# root@debian-squeeze:~# root@debian-squeeze:~# readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/ixgbevf root@debian-squeeze:~# /usr/local/libvirt/bin/virsh start new-installed Domain new-installed started root@debian-squeeze:~# readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub root@debian-squeeze:~# ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. >From 192.168.100.6 icmp_seq=1 Destination Host Unreachable >From 192.168.100.6 icmp_seq=2 Destination Host Unreachable >From 192.168.100.6 icmp_seq=5 Destination Host Unreachable >From 192.168.100.6 icmp_seq=6 Destination Host Unreachable >From 192.168.100.6 icmp_seq=7 Destination Host Unreachable >From 192.168.100.6 icmp_seq=8 Destination Host Unreachable ^C N ever came! Please suggest if there is any way out. Relevant kernel logs: Aug 21 18:28:34 debian-squeeze kernel: [ 290.068511] ixgbevf 0000:04:10.0: enabling device (0000 -> 0002) Aug 21 18:28:34 debian-squeeze kernel: [ 290.069216] ixgbevf 0000:04:10.0: enabling bus mastering Aug 21 18:28:34 debian-squeeze kernel: [ 290.082458] ixgbevf 0000:04:10.0: irq 127 for MSI/MSI-X Aug 21 18:28:34 debian-squeeze kernel: [ 290.082482] ixgbevf 0000:04:10.0: irq 128 for MSI/MSI-X Aug 21 18:28:34 debian-squeeze kernel: [ 290.082503] ixgbevf 0000:04:10.0: irq 129 for MSI/MSI-X Aug 21 18:28:34 debian-squeeze kernel: [ 290.141706] ixgbe 0000:04:00.0: eth0: Set MAC msg received from VF 0 Aug 21 18:28:34 debian-squeeze kernel: [ 290.142548] ixgbe 0000:04:00.0: eth0: Set LPE msg received from vf 0 Aug 21 18:28:34 debian-squeeze kernel: [ 290.150487] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready Aug 21 18:28:34 debian-squeeze kernel: [ 290.153637] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Aug 21 18:28:45 debian-squeeze ntpdate[40135]: step time server 202.190.183.188 offset -0.004582 sec Aug 21 18:28:46 debian-squeeze snmpd[39480]: IfIndex of an interface changed. Aug 21 18:29:39 debian-squeeze kernel: [ 355.486987] pci-stub 0000:04:10.0: claimed by stub Aug 21 18:29:39 debian-squeeze kernel: [ 355.826741] pci-stub 0000:04:10.0: enabling device (0000 -> 0002) Aug 21 18:29:40 debian-squeeze kernel: [ 356.484437] assign device 0:4:10.0 Aug 21 18:29:47 debian-squeeze kernel: [ 363.296117] kvm: 40206: cpu0 unhandled rdmsr: 0xc0010001 Aug 21 18:29:55 debian-squeeze kernel: [ 371.643998] ixgbe 0000:04:00.0: eth0: Set MAC msg received from VF 0 Aug 21 18:29:55 debian-squeeze kernel: [ 371.644661] ixgbe 0000:04:00.0: eth0: Set LPE msg received from vf 0 Aug 21 18:29:55 debian-squeeze kernel: [ 371.663095] pci-stub 0000:04:10.0: irq 127 for MSI/MSI-X Aug 21 18:29:55 debian-squeeze kernel: [ 371.694983] pci-stub 0000:04:10.0: irq 127 for MSI/MSI-X Aug 21 18:29:55 debian-squeeze kernel: [ 371.695009] pci-stub 0000:04:10.0: irq 128 for MSI/MSI-X Aug 21 18:29:55 debian-squeeze kernel: [ 371.758805] pci-stub 0000:04:10.0: irq 127 for MSI/MSI-X Aug 21 18:29:55 debian-squeeze kernel: [ 371.758833] pci-stub 0000:04:10.0: irq 128 for MSI/MSI-X Aug 21 18:29:55 debian-squeeze kernel: [ 371.758856] pci-stub 0000:04:10.0: irq 129 for MSI/MSI-X Regards, Rajesh Kumar Mallah Tel. 91-11-46710500 (Ext:303) Cell +919811255597 Website: http://www.tradeindia.com/ \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | start planting | | | ----- "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> wrote: | From: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | To: "Alex Jia" <ajia(a)redhat.com> | Cc: libvirt-users(a)redhat.com, "vikas pandey" <vikas_pandey(a)tradeindia.com> | Sent: Tuesday, August 21, 2012 11:00:24 AM | Subject: Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage. | | | Dear Alex , | | Thanks Once again for responding. I tried to replicate your steps. in our case readlink always reveals that the pci device is being | handled by the pci-stub driver (as in our case ixgbevf is absent in the host) | | Below is an annotaded sequence of events. | | Check status : # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub | | Content of the nic.xml: | root@debian-squeeze:/usr/local/libvirt/etc/libvirt/qemu# cat /root/nic.xml <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x04' slot='0x10' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </hostdev> # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub | | corrent connectivity is OK | # ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. 64 bytes from 192.168.101.10: icmp_req=1 ttl=64 time=0.491 ms 64 bytes from 192.168.101.10: icmp_req=2 ttl=64 time=0.384 ms 64 bytes from 192.168.101.10: icmp_req=3 ttl=64 time=0.310 ms ^C --- 192.168.101.10 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.310/0.395/0.491/0.074 ms # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub | | Detach and reattach and check connectivity in running guest. | note: the guest has pci hotplug support , the ethernet interfaces | are configured to allow hotplug and IP is statically assigned. | # virsh detach-device new-installed /root/nic.xml Device detached successfully # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub root@debian-squeeze:/usr/local/libvirt/etc/libvirt/qemu# ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. >From 192.168.100.6 icmp_seq=9 Destination Host Unreachable >From 192.168.100.6 icmp_seq=10 Destination Host Unreachable >From 192.168.100.6 icmp_seq=11 Destination Host Unreachable ^C --- 192.168.101.10 ping statistics --- 14 packets transmitted, 0 received, +3 errors, 100% packet loss, time 13096ms pipe 3 # virsh attach-device new-installed /root/nic.xml Device attached successfully # ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. 64 bytes from 192.168.101.10: icmp_req=1 ttl=64 time=0.507 ms 64 bytes from 192.168.101.10: icmp_req=2 ttl=64 time=0.388 ms 64 bytes from 192.168.101.10: icmp_req=3 ttl=64 time=0.314 ms 64 bytes from 192.168.101.10: icmp_req=4 ttl=64 time=0.315 ms 64 bytes from 192.168.101.10: icmp_req=5 ttl=64 time=0.335 ms ^C --- 192.168.101.10 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3998ms rtt min/avg/max/mdev = 0.314/0.371/0.507/0.076 ms # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub | Above proves that detach-attach cycle was successful. | # virsh detach-device new-installed /root/nic.xml Device detached successfully | | Please note that guest is being shutdown with nic detached. | | # virsh shutdown new-installed Domain new-installed is being shutdown | Guest being started again : | | # virsh start new-installed Domain new-installed started # ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. 64 bytes from 192.168.101.10: icmp_req=1 ttl=64 time=0.583 ms 64 bytes from 192.168.101.10: icmp_req=2 ttl=64 time=0.402 ms 64 bytes from 192.168.101.10: icmp_req=3 ttl=64 time=0.308 ms 64 bytes from 192.168.101.10: icmp_req=4 ttl=64 time=0.316 ms 64 bytes from 192.168.101.10: icmp_req=5 ttl=64 time=0.318 ms 64 bytes from 192.168.101.10: icmp_req=6 ttl=64 time=0.247 ms ^C --- 192.168.101.10 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 4997ms rtt min/avg/max/mdev = 0.247/0.362/0.583/0.109 ms | Please note on starting the guest the PCI device came up | and connectivity was established. The device was also defined | inside the guest XML. | | | Now shutting down the Guest without detaching. | | # virsh shutdown new-installed Domain new-installed is being shutdown # virsh start new-installed Domain new-installed started | | # ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. >From 192.168.100.6 icmp_seq=9 Destination Host Unreachable >From 192.168.100.6 icmp_seq=10 Destination Host Unreachable >From 192.168.100.6 icmp_seq=11 Destination Host Unreachable ^C --- 192.168.101.10 ping statistics --- 14 packets transmitted, 0 received, +3 errors, 100% packet loss, time 13095ms pipe 3 CONNECTION IS LOST | | We are using latest libvirtd (0.9.13) , lastest ixgbe/ixgbevf (from sf) , lastest stable kernel (3.5.1) | | Regards, | Rajesh Kumar Mallah | Tel. 91-11-46710500 (Ext:303) | Cell +919811255597 | Website: http://www.tradeindia.com/ | \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | | start planting | | | | | | ----- "Alex Jia" <ajia(a)redhat.com> wrote: | | From: "Alex Jia" <ajia(a)redhat.com> | | To: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | | Cc: libvirt-users(a)redhat.com | | Sent: Tuesday, August 21, 2012 9:34:24 AM | | Subject: Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage. | | | | On 08/21/2012 11:22 AM, Rajesh Kumar Mallah wrote: | | | | Dear Alex / List , | | | | Thanks for the response. | | | | The problem is regarding detaching from the guest not host. | | | | I see, if you attach a PCI device into guest with 'managed' mode(managed='yes') then the device is automatically detached from guest and returned to host after guest exiting, for example. | | | | # lspci | grep Eth | | 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) | | | | # readlink /sys/bus/pci/devices/0000\:00\:19.0/driver/ -f | | /sys/bus/pci/drivers/e1000e | | | | # virsh start foo | | Domain foo started | | | | # ping -c 3 xx.xx.xx.xx | | PING xx.xx.xx.xx (xx.xx.xx.xx) 56(84) bytes of data. | | 64 bytes from nx-in-f160.1e100.net (xx.xx.xx.xx): icmp_seq=1 ttl=49 time=87.8 ms | | 64 bytes from nx-in-f160.1e100.net (xx.xx.xx.xx): icmp_seq=2 ttl=49 time=85.2 ms | | 64 bytes from nx-in-f160.1e100.net (xx.xx.xx.xx): icmp_seq=3 ttl=49 time=91.8 ms | | --- xx.xx.xx.xx ping statistics --- | | 3 packets transmitted, 3 received, 0% packet loss, time 2093ms | | rtt min/avg/max/mdev = 85.240/88.327/91.881/2.731 ms | | | | # cat hostdev.xml | | <hostdev mode='subsystem' type='pci' managed='yes'> | | <source> | | <address domain='0x0000' bus='0x00' slot='0x19' function='0x0'/> | | </source> | | </hostdev> | | | | # virsh attach-device foo hostdev.xml | | Device attached successfully | | | | # readlink /sys/bus/pci/devices/0000\:00\:19.0/driver/ -f | | /sys/bus/pci/drivers/pci-stub | | | | # ping -c 3 xx.xx.xx.xx | | connect: Network is unreachable | | | | # virsh destroy foo | | Domain foo destroyed | | | | # readlink /sys/bus/pci/devices/0000\:00\:19.0/driver/ -f | | /sys/bus/pci/drivers/e1000e | | | | # ping -c 3 xx.xx.xx.xx | | PING xx.xx.xx.xx (xx.xx.xx.xx) 56(84) bytes of data. | | 64 bytes from xx.xx.xx.xx: icmp_seq=1 ttl=49 time=79.7 ms | | 64 bytes from xx.xx.xx.xx: icmp_seq=2 ttl=49 time=83.2 ms | | 64 bytes from xx.xx.xx.xx: icmp_seq=3 ttl=49 time=84.5 ms | | | | --- xx.xx.xx.xx ping statistics --- | | 3 packets transmitted, 3 received, 0% packet loss, time 2087ms | | rtt min/avg/max/mdev = 79.714/82.480/84.513/2.040 ms | | | | Notes, need to wait for local network recovery again then check network connectivity. | | | | If your network still is disconnect, it may be a bug IMHO, please show your libvirt | | and qemu-kvm version, or my example is not what you want, please let me know. | | | | Thanks, | | Alex | | | | | | In our case since ixgbevf driver is NOT present in the host hence the virtual | | interfaces never really attach themselves to the host. | | | | Regards, | | Rajesh Kumar Mallah | | Tel. 91-11-46710500 (Ext:303) | | Cell +919811255597 | | Website: http://www.tradeindia.com/ | | \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | | | start planting | | | | | | | | | ----- "Alex Jia" <ajia(a)redhat.com> wrote: | | | From: "Alex Jia" <ajia(a)redhat.com> | | | To: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | | | Cc: libvirt-users(a)redhat.com | | | Sent: Tuesday, August 21, 2012 8:31:21 AM | | | Subject: Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage. | | | | | | On 08/20/2012 08:34 PM, Rajesh Kumar Mallah wrote: Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of the guests. Dear Rajesh, | | | | | | Please see the following comments. | | | | | | ( the detach is explicitly done via virsh command /usr/local/libvirt/bin/virsh detach-device guest01 ~/nic.xml nic.xml contained <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x04' slot='0x10' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </hostdev> ) The question is anyone else facing similar problem and if so what solution was used? Secondly , is there anyway to automate the detaching of the VFs from the guest when the guest is put in the shutdown sequence ? (or for that matter destroyed). | | | When managed is "yes" for a PCI device, it is automatically detached from the host before being passed on to the guest, and automatically reattached to the host after the guest exits such as shutdown a guest. | | | | | | Regards, | | | Alex | | | | | | Regards, Rajesh Kumar Mallah Tel. 91-11-46710500 (Ext:303) Cell +919811255597 Website: http://www.tradeindia.com/ \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | start planting | | | _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users | | | | |

2 5

[libvirt-users] remote lxc via libvirt?
by Dan Kegel 27 Aug '12

27 Aug '12

Has support for creating or using lxc containers on remote machines been added to libvirt yet? https://help.ubuntu.com/12.04/serverguide/lxc.html says "Libvirt is a powerful hypervisor management solution with which you can administer Qemu, Xen and LXC virtual machines, both locally and remote." so I assume it's been done and I'm just having trouble seeing it... otoh, I hear libvirt-lxc is going to be rewritten on top of liblxc Real Soon Now, maybe that has some bearing on the question.

2 1

[libvirt-users] Does libvirt abstract each and any vm specific command?
by adrelanos 25 Aug '12

25 Aug '12

Hello, my project still uses VBoxManage but I am inclined to switch to libvirt, if possible, because I like the concept. Some rather unusual commands are used by my project... VBoxManage modifyvm "$VMNAME" --synthcpu on VBoxManage setextradata "$VMNAME" "VBoxInternal/Devices/VMMDev/0/Config/GetHostTimeDisabled" "1" VBoxManage modifyvm "$VMNAME" --natdnsproxy1 on VBoxManage modifyvm "$VMNAME" --natdnshostresolver1 on VBoxManage modifyvm "$VMNAME" --natdnspassdomain1 off I haven't found any mention of synthcpu, GetHostTimeDisabled, etc. on libvirt.org. Does libvirt abstract each any any vm specific command? Or only the most common ones? So, if I say, I really need the commands listed above, I can't use libvirt? Cheers, adrelanos

2 1