similar to: virsh edit problems

Displaying 20 results from an estimated 20000 matches similar to: "virsh edit problems"

2019 Oct 10
2
Fwd: Libvirt-QEMU : Multiplex the output from qemu's serial port to a pty as well as a file (basically redirect console to file as well as pty device)
Hi Folks , As per https://libvirt.org/formatdomain.html#elementsConsole Regardless of the type, character devices can have an optional log file associated with them. Whether the lgging functionality is same as mapping device to file ? Whether libvirt xml syntax below both 1 and 2 are same ? 1) <serial type='pty'> <log
2012 May 08
1
virsh console logging and pty usage
Is it possible to both log the serial console and to actually use it? A few of the VMs I've got are configured as follows: <serial type='file'> <source path='/var/log/libvirt/qemu/serial/bb-2.6.18-128.el5-x86_64.log'/> <target port='0'/> </serial> <console type='file'> <source
2018 Nov 29
2
Re: console type tcp with logging
чт, 29 нояб. 2018 г. в 18:23, Daniel P. Berrangé <berrange@redhat.com>: > > On Thu, Nov 29, 2018 at 06:19:43PM +0300, Vasiliy Tolstov wrote: > > Hi! I want to have ability to connect to guest console via libvirt api > > (and expose this data to xtermjs via websocket) with getty tty. And > > also i want to have log of tty1 (do log grub, kernel booting and > >
2010 Jun 03
1
Virsh blkstat doesn't work on Xen HVM
Hi I tried to use virsh blkstat to get information of a block, but it returns an error message as shown below This function works fine in KVM, but fail in XEN. I tried XEN 3.4.3 ,4.0.0 and 4.0.1 with libvirt 0.7.1 from fedora yum server and 0.8.1 from libvirt . All of them are fail to get the block status. The following is the config file and error message of virsh domblkstat. Any one
2020 Sep 20
1
redirecting guest serial to file on the host
Greetings, I have a vm to which I can access using virsh console vm1/ I'd like in addition to be able to dump the serial of the vm in to a file on the host. I've found this https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sub-section-libvirt-dom-xml-devices-host-interface but it seems that the first second example which
2019 Oct 11
0
Fwd: Libvirt-QEMU : Multiplex the output from qemu's serial port to a pty as well as a file (basically redirect console to file as well as pty device)
+dev Hi Folks , As per https://libvirt.org/formatdomain.html#elementsConsole Regardless of the type, character devices can have an optional log file associated with them. Whether the lgging functionality is same as mapping device to file ? Whether libvirt xml syntax below both 1 and 2 are same ? 1) <serial type='pty'> <log
2018 Dec 01
2
Re: console type tcp with logging
пт, 30 нояб. 2018 г. в 12:43, Daniel P. Berrangé <berrange@redhat.com>: > > On Thu, Nov 29, 2018 at 08:57:54PM +0300, Vasiliy Tolstov wrote: > > чт, 29 нояб. 2018 г. в 18:23, Daniel P. Berrangé <berrange@redhat.com>: > > > > > > On Thu, Nov 29, 2018 at 06:19:43PM +0300, Vasiliy Tolstov wrote: > > > > Hi! I want to have ability to connect to
2018 Sep 14
0
virsh doesn't support vtpm using XEN?
Hi again! More TPM + XEN stuff. have look at the following: ================= "xl list -l centos7.0" ============== [ { "domid": 31, "config": { "c_info": { "type": "hvm", "name": "centos7.0", "uuid":
2009 Oct 10
2
virsh dumpxml didn''t reflect viridian=1
Just the output of one of the viridian enabled windows hvm machines: Florian virsh dumpxml titan <domain type=''xen'' id=''40''> <name>titan</name> <uuid>cedb6201-82d6-3c96-4da3-e0bfad6a7501</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>2</vcpu> <os>
2009 Oct 10
2
virsh dumpxml didn''t reflect viridian=1
Just the output of one of the viridian enabled windows hvm machines: Florian virsh dumpxml titan <domain type=''xen'' id=''40''> <name>titan</name> <uuid>cedb6201-82d6-3c96-4da3-e0bfad6a7501</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>2</vcpu> <os>
2009 Nov 23
1
64bit guest on top of 64bit hypervisor+dom0 does not boot with virsh while it does with xm command
I installed xen on top of Cent OS 5.3 64bit OS with gitco rpm sources. Everything works fine except that I can''t run 64bit pv guest with virsh command. With xm commands I can load the same guest. 32bit pv guest, 32 bit and 64bit hvm works fine with both virsh and xm command. Has anyon have any idea? any help will be largely appreciated. **This is dumpxml for 64bit configuration* **
2014 Jul 07
1
virsh: cannot start domain with channel device,
Here is what I got. root ubuntu:/home/john# virsh start ubuntu2 error: Failed to start domain ubuntu2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/1 bind(unix:/var/lib/libvirt/qemu/ubuntu2.libguestfs): Permission denied chardev: opening backend "socket" failed: Permission denied root ubuntu:/home/john# ll
2018 Nov 12
1
virsh reboot "in shutdown" state?
Hi all, I've got a weird issue, and I'm trying to confirm if it's a bug, and if so, if there is a workaround until it is fixed. The situation is this: If I virsh reboot <domain> --mode acpi, it will actually reboot the domain cleanly (watching from the console allows me to see the full shutdown messages, followed by a bootup). However, after this point, virsh domstate
2015 Aug 12
2
PCI passthrough fails in virsh: iommu group is not viable
I would really appreciate some pointers on what I am doing wrong here. I have a need to run multiple virtual guests which have each their own GPU and some USB controllers passed-through. I am able to run one of the guests like this (assuming vfio stuff has happened elsewhere), but I would prefer to use virsh: kvm -M q35 -m 8192 -cpu host,kvm=off \ -smp 4,sockets=1,cores=4,threads=1 \ -bios
2015 Mar 19
2
pty pairing host - guest
HI!, I am using virt-manager GUI. There I can add a `Console Device` through Add Hardware. I can add a virtio pty WITHOUT restarting the VM. also I get a pty allocated to host machine say `/dev/pty/M` My expectation is this `host:/dev/pty/M` is connected with a `guest:/dev/ttyN`. so If I open minicom or screen and write to `host:/dev/pty/M` it will be propagated to 'guest:/dev/ttyN'. Is
2013 Jul 12
2
libvrtd-1.1.0 crashes when attempting to start some (but not all) LXC containers
Hello all, I have two issues: 1) I am unable to start a seemingly correct LXC domain (I cloned it from a working domain). 2) I am able to crash "libvirtd" by attempting to start the cloned domain, but starting the original works just fine. I humbly submit that item #2 is a bug - the "libvirtd" daemon should never crash due to anything the "libvirt" client
2017 Oct 19
2
terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu
2015 Jul 09
2
adding devices and chardev in .xml configuration file ...
Hi, As I want to start qemu by adding following parameters : -device virtio-serial -chardev socket,path=/tmp/foo,server,nowait,id=test -device virtserialport,chardev=test,name=port.0 Is it possible to add them in the .xml configuration file of the guest , so they will be automatically added when the guest is started ? If yes , any doc describing the syntax ? Thx. Regards, J.P. Ribeauville
2018 Nov 29
2
console type tcp with logging
Hi! I want to have ability to connect to guest console via libvirt api (and expose this data to xtermjs via websocket) with getty tty. And also i want to have log of tty1 (do log grub, kernel booting and errors). What i need to do in libvirt xml for such case? -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru
2012 Dec 20
1
Error installing VM: "Process exited while reading console log output"
Hi, I'm trying to install a qemu-kvm virtual machine on a Debian GNU/Linux squeeze amd64 host, using virtinst 0.500.3 and libvirt 0.8.3. First I tried this command as a normal user (in groups kvm and libvirt): $ virt-install --connect qemu:///system --name test1 \ > --ram $((128 * 1024 * 1024)) --vcpus=1 --description 'Test VM 1' \ >