similar to: [libivrt-user]problem when using qemu 2.0.0 + libvirt 1.2.6

Hi I got a problem when using qemu 2.0.0 + libvirt 1.2.6 . It just can not define a kvm vm successfully , errors like this : # virsh define 5ab4f49c-c99f-4dbd-9d7d-17a946b4c5a7.xml error: Failed to define domain from 5ab4f49c-c99f-4dbd-9d7d-17a946b4c5a7.xml error: unknown OS type hvm After several tries, i found that Qemu2.0 /qemu-kvm1.2+ libvirt1.0.2 and lower version is ok Qemu2.0

On 07/29/2014 08:39 PM, weiwei li wrote: > Hi > I got a problem when using qemu 2.0.0 + libvirt 1.2.6 . It just can not > define a kvm vm successfully , errors like this : > > # virsh define 5ab4f49c-c99f-4dbd-9d7d-17a946b4c5a7.xml > error: Failed to define domain from 5ab4f49c-c99f-4dbd-9d7d-17a946b4c5a7.xml > error: unknown OS type hvm Can you show the actual contents of

Hi, Weeks ago, I developed my app under ubuntu-11.10 (kernel 3.0) with lilbvirt-0.9.10. In my code , I used virDomainGetCPUStats to query cpu usage info of domains, and it worked well. However, today, I port my code to ubuntu-10.04.4 (kernel 2.6.32) with libvirt-0.9.10, I find the function virDomainGetCPUStats can't work and complains "this function is not supported by the connection

On 11/19/2013 06:58 PM, Guozhonghua wrote: > Libivrt 1.1.0 > Migrate VM between two hosts using shell scripts. Can you please retry with libvirt 1.1.4? There have been some bug fixes in this area, and it's not worth debugging old versions if the new version is already fixed. > This e-mail and its attachments contain confidential information from H3C, which is Such a disclaimer is

Hi, I created an LXC domain via libvirt (on Fedora 20), but when I'm trying to mount a FUSE filesystem, like sshfs, I'm getting a following error: $ sshfs 172.30.15.2:/<mntdir> /<mntpoint> fuse: device not found, try 'modprobe fuse' first I see that there's no /dev/fuse device. Is there a way to make it work? Can I get it working via libvirt domain xml file

On 12/19/2013 05:16 AM, Eldar Yusupov wrote: > Hi, > > I created an LXC domain via libvirt (on Fedora 20), but when I'm trying to mount a FUSE filesystem, like sshfs, I'm getting a following error: > > $ sshfs 172.30.15.2:/<mntdir> /<mntpoint> > fuse: device not found, try 'modprobe fuse' first > > I see that there's no /dev/fuse device.

On 10/12/20 9:47 PM, Talha Jawaid wrote: > Hello, > > I want to run a python script on Windows to remotely control libvirt > running on a (Linux) server. This was all working fine while prototyping > stuff on the server but now I am having some trouble installing the > python module on windows (“pip install” fails). I struggled through > getting it to COMPILE but then ran

Libivrt 1.1.0 Migrate VM between two hosts using shell scripts. The issues is occurred about every 5 minutes, using gdb and the back trace is below: (gdb) c Continuing. [New Thread 0x7f78e7c11700 (LWP 48116)] [New Thread 0x7f78cf7fe700 (LWP 48129)] [New Thread 0x7f78ceffd700 (LWP 48306)] [New Thread 0x7f78ce7fc700 (LWP 62351)] [New Thread 0x7f78cdffb700 (LWP 62694)] Program received signal

uname -a SunOS i7 5.11 snv_114 i86pc i386 i86xpv The box is a core i7 with 6GB of RAM. The command virt-install --name 10u7 --ram 1024 --hvm --file /guests/10u7 --os-type=solaris os-variant=solaris10 --location /export/iso/sol-10-u7-ga-x86-dvd.iso get as far as opening the VNC client, when I select Solaris from grub, the OS starts to boot then panics, closing the session. So I

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next