search for: qmeu

...not want a frame buffer. Neither a paravirtualised one, nor an emulated one. With xm my guests have hvc0 as a console and that works perfectly for me. Xen obviously doesn’t need qemu-dm and I don’t need qemu-dm, so how do I convince xl to start a guest without trying to emulate some hardware with qmeu-dm? Thanks, Lloyd p.s. For reference, here is my guest configuration. The “builder” line is commented out when I use xm of course. builder = “generic" kernel = "/netbsd-612-XEN3_DOMU.gz" memory = 1024 name = “domu" vcpus = 1 vif = [ ''bridge=bridge0'' ] disk...

Not that I know of, resource usage seems totally normal. Also, as I mentioned, virt-install and virt-manager can both access and run vm's on qmeu without any trouble. Ulimit is also unset. On Fri, Jan 24, 2014 at 2:42 PM, Richard W.M. Jones <rjones@redhat.com>wrote: > On Fri, Jan 24, 2014 at 12:45:43PM -0800, Tim Fall wrote: > > Here’s the trace you requested. I can dump the text if the > > attachment doesn’t work. &g...

...very slow. > On the host you can see that the qemu-system-x86_64 process is using just one core! > > Ppc64le guests are using multi cores, so its looks like an config problem or software bug with the x86 emulator. snip > Does anybody knows this problem? You've not mentioned what QMEU version or what libvirt version you have. Historically though emulation was single threaded. Only with MTTCG has it become multi-threaded and thus able to use all cores for vCPUs. THat is a few years old now though, so most distros should have MTTCG in some form or another if reasonably up2date....

...http://wiki.qemu.org/Documentation/CreateSnapshot) make it sound like you simply point your qemu at the snapshot after it's creation, and you're golden. When attempting this with libvirt, though, it fails. I created a snapshot using the above tutorial. the resulting file is disk.0, and a qmeu-img info on it returns: image: disk.0 file format: qcow2 virtual size: 29G (31457280000 bytes) disk size: 140K cluster_size: 65536 backing file: /var/lib/one/public/lin_client_current.qcow2 (actual path: /var/lib/one/public/lin_client_current.qcow2) So that all looks groovy, right? Then, I creat...

...re. >> >> This depends on the status setting from guest or userspace. Which >> means it can not deal with e.g when qemu or userspace is crashed? Do >> we need to care this or it's a over engineering? >> >> Thanks > If qemu crash, I guess users may re-run qmeu / re-initialize the device, according to the spec, there should be a reset routine. > This code piece handles status change on DRIVER_OK flipping. I am not sure I get your point, mind to give more hints? The problem is if we don't launch new qemu instance, the interrupt will be still ther...

...is no error output #!/usr/bin/python import socket s=socket.socket(socket.AF_UNIX,socket.SOCK_STREAM) s.connect("/var/lib/libvirt/qemu/r-22-VM.agent") s.send("test\n") s.close 3. But i not read date in vm device /dev/vport0p1 (vm is run) My version, libvirt: 1.2.13.1 qmeu: 2.3.0 system: centos 6.5 This test in libvirt 1.0.5.7 qemu 1.5.3 is success. Please help , thanks

...orrectly detects my host CPU as Westmere: $ virsh capabilities | grep model <model>Westmere</model> qemu-kvm does (as far as I can tell) support Nehalem: $ qemu-kvm -cpu ?model | grep Nehalem x86 Nehalem Intel Core i7 9xx (Nehalem Class Core i7) Nehalem is defined in qmeu's target-x86_64.conf: grep Nehalem /etc/qemu/target-x86_64.conf name = "Nehalem" model_id = "Intel Core i7 9xx (Nehalem Class Core i7)" And if I run a cpu check on the processor, it seems to work fine: $ qemu-kvm -cpu Nehalem,check VNC server running on `127.0.0.1:5...

[This email is either empty or too large to be displayed at this time]

On Fri, Jan 24, 2014 at 04:49:24PM -0800, Tim Fall wrote: > Not that I know of, resource usage seems totally normal. Also, as I > mentioned, virt-install and virt-manager can both access and run vm's on > qmeu without any trouble. Ulimit is also unset. You can try a different qemu from upstream, which should diagnose whether this is a kernel problem or a qemu problem: ---------------------------------------------------------------------- git clone git://git.qemu.org/qemu.git cd qemu sudo apt-get buil...

...orm Guru Mozilla Corporation benjamin at smedbergs.us http://benjamin.smedbergs.us/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHxM1DSSwGp5sTYNkRArvnAKCM97BS4xNVPiA3AWLvsveumrJ1kgCfTo9T I+yBqj71gmIyzkNJObXsOCs= =QMeu -----END PGP SIGNATURE-----

Subject says it all. Looking in /usr/include/gnu, I find stubs-64.h and stubs.h, but no stubs-32.h. This is probably related to my machine running a 64-bit install of Ubuntu. I'm not sure whether this should be rectified in Ubuntu or LLVM. Regards, Jo

When hotplug hvm vcpu by ''xm vcpu-set'' command, if it add/remove many vcpus by 1 ''xm vcpu-set'' command, it has a bug that it cannot add/remove all vcpus that want to be added/removed. This patch is to fix the bug. It delays trigger sci until all xenstore cpu node status are watched. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com>

Hi, thanks for great job do with xen .deb, we have a problem on xen 3.4.2 (certainly not just us) how is impossibile do hvm domu work because there isn't qemu-dm, i read a few months ago discussion of this but also now there is the problem, will be resolved soon? it possibile rebuild the current package with the simple addition of qemu? thanks in advance for any reply -------------- next

...2 11:45:39.091+0000: 32314: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous 2018-05-22 11:45:41.841+0000: 32310: error : qemuMonitorIO:615 : internal error End of file from monitor the qmeu-kvminstance-00001959.log: 2018-05-22 11:45:38.603+0000: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/home/ning.zhao USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name instance-00001959 -S -M rhel6.6.0 -cpu Broadwell,+abm,+pdpe1gb,+rdrand,+f16c,+osxsave,+dca,+pdc...

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and