[libvirt-users] 转发: Error when executing virsh command to ESX
by li_fuqiong
To Whom It May concern:
I found that the following error is caused by adding a scsi disk to install the os, I remove the scsi disk and the error remove but still report 'out of memory':
virsh # dumpxml win2003_122
internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp
x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName'
virsh # list --all
Id Name State
----------------------------------
80 win2003_122 running
- winxp121 shut off
virsh # nodeinfo
error: failed to get node information
error: out of memory
virsh # dumpxml win2003_122
error: out of memory
li_fuqiong
发件人： li_fuqiong
发送时间： 2012-03-21 15:24
收件人： libvirt-users
主题： Error when executing virsh command to ESX
To Whom It May Concern:
I use virsh windows 0.9.3 to connect an esx server 4.0 with no_verify=1. The Esx server is intel 2 x 3.19 GHZ CPU, 8G memroy and 2 TB hard disk.
following is my execute commands and results.
virsh -c esx://xxx.xxx.xxx.x?no_verify=1
virsh # list all
Id Name State
----------------------------------
80 win2003_122 running
virsh # nodeinfo
error: failed to get node information
error: out of memory
virsh # dumpxml win2003_122
error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp
x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName'
virsh # edit win2003_122
error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp
x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName'
virsh # destroy win2003_122
Domain win2003_122 destroyed
virsh # start win2003_122
Domain win2003_122 started
virsh # edit win2003_122
error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp
x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName'
question:
1.Why error when executeing dumpxml and edit command? How to fix it?
2.Why out of memory when nodeinfo. How to fix it? I have only one test vm on my esx server.
Thanks in advance.
Mark
12 years, 7 months
Re: [libvirt-users] [libvirt] Problem with Open vSwitch and dnsmasq
by Daniele Milani
> Date: Thu, 22 Mar 2012 15:11:44 -0400
> From: laine(a)laine.org
> To: libvir-list(a)redhat.com
> Subject: Re: [libvirt] Problem with Open vSwitch and dnsmasq
>
> On 03/22/2012 09:10 AM, Daniele Milani wrote:
> > Dear all,
> > I have the following situation:
> > -I replaced the standard bridge driver with the Open VSwitch one;
>
> I'm curious what you mean by this.
>
> libvirt's virtual networks currently only support the standard linux
> bridge device. There is no code in libvirt to use openvswitch devices
> for libvirt's virtual networks. The openvswitch support in libvirt only
> applies to guest devices that use <interface type='bridge'>.
>
> >From your message, it sounds like there is a driver that that replaces
> the linux host bridge driver with something that emulates that driver,
> but is actually an openvswitch bridge on the backend. I hadn't
> previously heard of this.
> I did it by installing Open vSwitch with kernel modules:
% ./configure --with-linux=/lib/modules/`uname -r`/build
after that I replaced the standard linux bridge driver by executing:
% rmmod bridge
% insmod datapath/linux/brcompat.ko% ovs-brcompatd --pidfile --detachyou can find all this information at:
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=IN...
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=IN...
Daniele Milani
>
> > -I started a NAT-network on Libvirt (bridge name virbr1);
> > -I started a Virtual Machine (VM1) on Libvirt, and I tagged his
> > interface (vnet0) with tag=2;
> > -if I run "# ovs-vsctl show" I obtain:
> >
> > Bridge "virbr1"
> > Port "vnet0"
> > tag: 2
> > Interface "vnet0"
> > Port "virbr1-nic"
> > Interface "virb1-nic"
> > Port "virbr1"
> > Interface "virbr1"
> > type: internal
> >
> > -the problem is that it is impossible to assign to VM1 an IP, because
> > the dnsmasq daemon does not accept the tagged DHCP Discover frame.
> >
> > Does someone know if there is a way for dnsmasq to accept tagged
> > frames through "virbr1", and send a tagged DHCP Offer packet back to VM1?
>
>
> --
> libvir-list mailing list
> libvir-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/libvir-list
12 years, 7 months
Re: [libvirt-users] [libvirt] Problem with Open vSwitch and dnsmasq
by Laine Stump
(Cc'ing to libvirt-users(a)redhat.com)
On 03/22/2012 02:43 PM, Ansis Atteka wrote:
>
>
> On Thu, Mar 22, 2012 at 11:11 AM, Daniele Milani <dano1988(a)hotmail.it
> <mailto:dano1988@hotmail.it>> wrote:
>
> I think I could try the first solution. Can you explain me how do
> I create the port used by dnsmasq?
>
> For example, is it correct to execute
> # ovs-vsctl add-port virbr1 port2 tag=2
> to create a port for the vLan whose tag is 2 named "port2"?
>
>
> Try something like this:
>
> ovs-vsctl add-port virbr1 port2 tag=2
> ovs-vsctl set Interface port2 type=internal
> ifconfig port2 10.0.0.1
> ifconfig port2 up
> /usr/sbin/dnsmasq --strict-order --bind-interfaces
> --except-interface lo --listen-address 10.0.0.1 --dhcp-range
> 10.0.0.10,10.0.0.20
> --dhcp-leasefile=/var/lib/libvirt/dnsmasq/vlan2.leases
> --dhcp-lease-max=253 --dhcp-no-override
>
By the time you are doing this much stuff outside of libvirt, I think it
would really be better to not use a libvirt virtual network at all,
since libvirt is likely to do things to that network that would end up
breaking the config you've done outside of libvirt.
Instead, just use the host OS configuration files to create the bridge,
add the tagged port, run dnsmasq, etc., then use <interface
type='bridge'> in the guest rather than <interface type='network'>
> Though I have not tested it...
>
>
> Daniele Milani
>
>
> Date: Thu, 22 Mar 2012 10:54:21 -0700
> Subject: Re: [libvirt] Problem with Open vSwitch and dnsmasq
> From: aatteka(a)nicira.com <mailto:aatteka@nicira.com>
> To: dano1988(a)hotmail.it <mailto:dano1988@hotmail.it>
> CC: libvir-list(a)redhat.com <mailto:libvir-list@redhat.com>;
> roberto.sassu(a)polito.it <mailto:roberto.sassu@polito.it>
>
>
>
>
> On Thu, Mar 22, 2012 at 6:10 AM, Daniele Milani
> <dano1988(a)hotmail.it <mailto:dano1988@hotmail.it>> wrote:
>
> Dear all,
> I have the following situation:
> -I replaced the standard bridge driver with the Open VSwitch one;
> -I started a NAT-network on Libvirt (bridge name virbr1);
> -I started a Virtual Machine (VM1) on Libvirt, and I tagged
> his interface (vnet0) with tag=2;
> -if I run "# ovs-vsctl show" I obtain:
>
> Bridge "virbr1"
> Port "vnet0"
> tag: 2
> Interface "vnet0"
> Port "virbr1-nic"
> Interface "virb1-nic"
> Port "virbr1"
> Interface "virbr1"
> type: internal
>
> -the problem is that it is impossible to assign to VM1 an IP,
> because the dnsmasq daemon does not accept the tagged DHCP
> Discover frame.
>
> Does someone know if there is a way for dnsmasq to accept
> tagged frames through "virbr1", and send a tagged DHCP Offer
> packet back to VM1?
>
> I believe you would need to run dedicated dnsmasq process instance
> per each VLAN that you have. By
> default I guess dnsmasq runs on virbr1, hence it does not see the
> tagged traffic that comes from vnet0.
>
> You could try to:
>
> 1. add another port to that bridge with the same VLAN as VM has.
> And run a separate instance of dnsmasq there; or
>
>
>
>
> change the tag of virb1 port, but this might lead to other issues
> (e.g. then non-tagged VMs will not get DHCP leases).
> Perhaps someone else can suggest something easier...
>
> Greetings,
> Daniele Milani
>
>
> --
> libvir-list mailing list
> libvir-list(a)redhat.com <mailto:libvir-list@redhat.com>
> https://www.redhat.com/mailman/listinfo/libvir-list
>
>
>
>
>
> --
> libvir-list mailing list
> libvir-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/libvir-list
12 years, 7 months
[libvirt-users] Does libvirt check MCS labels during hot-add disk image ?
by Onkar N Mahajan
Libvirt doesn't care about security during hot add disk images. It even
accepts addition of disk images of other guest running on the host.
Steps followed to create this scenario :
Started two VMs with following security configurations:
vm1:
<seclabel type='dynamic' model='selinux' relabel='yes'>
<label>system_u:system_r:svirt_t:s0:c219,c564</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c219,c564</imagelabel>
</seclabel>
vm2 :
<seclabel type='dynamic' model='selinux' relabel='yes'>
<label>system_u:system_r:svirt_t:s0:c122,c658</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c122,c658</imagelabel>
</seclabel>
# virsh list --all
Id Name State
----------------------------------
28 vm1 running
29 vm2 running
# ls -lZ /var/lib/libvirt/images/
-rw-------. qemu qemu system_u:object_r:svirt_image_t:s0:c219,c564
vm1.img
-rw-------. qemu qemu system_u:object_r:svirt_image_t:s0:c122,c658
vm2.img
# ps auxZ | grep qemu-kvm | grep -v grep
system_u:system_r:svirt_t:s0:c219,c564 qemu 15744 47.2 5.8 2757852
472224 ? Sl 11:47 0:18 /usr/libexec/qemu-kvm -S -M rhel6.2.0
-enable-kvm -m 2048 -smp 4,sockets=4,cores=1,threads=1 -name vm1 -uuid
d3d3a3ee-4edf-a3d3-8dab-a77740266270 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/var/lib/libvirt/images/vm1.img,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:a1:29:45,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
system_u:system_r:svirt_t:s0:c122,c658 qemu 15780 58.4 6.5 3063496
524048 ? Sl 11:47 0:20 /usr/libexec/qemu-kvm -S -M rhel6.2.0
-enable-kvm -m 2048 -smp 4,sockets=4,cores=1,threads=1 -name vm2 -uuid
b07607f8-2d03-cc1f-272b-22863667d1a4 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/var/lib/libvirt/images/vm2.img,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e0:76:d1,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
Now, try to add vm1's disk image into vm2 - this must not be allowed -
since for virtualized guest images. Only svirt_t processes with the
same MCS fields can read/write these images. i.e., for vm2 to access
vm1's disk image it's MCS label must be 's0:c660,c689'.
Hot addition of vm1's image i.e., /var/lib/libvirt/images/vm1.img is
successful ( which must not be allowed )
moreover , MCS label for vm1's image has changed to that of vm2
# ls -lZ /var/lib/libvirt/images/
-rw-------. qemu qemu system_u:object_r:svirt_image_t:s0:c122,c658
vm1.img
-rw-------. qemu qemu system_u:object_r:svirt_image_t:s0:c122,c658
vm2.img
Trying to read/write on vm1 will generate AVC messages
Seen following message in /var/log/audit/audit.log :
type=VIRT_RESOURCE msg=audit(1332310867.790:10312): user pid=5114 uid=0
auid=0 ses=3 subj=unconfined_u:system_r:virtd_t:s0-s0:c0.c1023
msg='virt=kvm resrc=disk reason=attach vm="vm2"
uuid=b07607f8-2d03-cc1f-272b-22863667d1a4 old-disk="?"
new-disk="/var/lib/libvirt/images/vm1.img":
exe=2F7573722F7362696E2F6C69627669727464202864656C6574656429 hostname=?
addr=? terminal=? res=success'
type=AVC msg=audit(1332310963.333:10313): avc: denied { write } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310963.333:10313): arch=c000003e syscall=18
success=no exit=-13 a0=9 a1=7fd3bc59d000 a2=1000 a3=10891b000 items=0
ppid=1 pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107
egid=107 sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
type=AVC msg=audit(1332310963.337:10314): avc: denied { read } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310963.337:10314): arch=c000003e syscall=295
success=no exit=-13 a0=9 a1=2d24368 a2=4 a3=88664000 items=0 ppid=1
pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107 egid=107
sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
type=AVC msg=audit(1332310963.338:10315): avc: denied { read } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310963.338:10315): arch=c000003e syscall=17
success=no exit=-13 a0=9 a1=7fd3bce4f000 a2=1000 a3=88664000 items=0
ppid=1 pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107
egid=107 sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
type=AVC msg=audit(1332310967.954:10316): avc: denied { read } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310967.954:10316): arch=c000003e syscall=295
success=no exit=-13 a0=9 a1=2d43768 a2=3 a3=1907c8000 items=0 ppid=1
pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107 egid=107
sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
type=AVC msg=audit(1332310967.955:10317): avc: denied { read } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310967.955:10317): arch=c000003e syscall=17
success=no exit=-13 a0=9 a1=7fd3bac95000 a2=1000 a3=1907c8000 items=0
ppid=1 pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107
egid=107 sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
type=AVC msg=audit(1332310968.594:10318): avc: denied { write } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310968.594:10318): arch=c000003e syscall=18
success=no exit=-13 a0=9 a1=7fd3bded9000 a2=1000 a3=2c3f000 items=0
ppid=1 pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107
egid=107 sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
type=AVC msg=audit(1332310968.594:10319): avc: denied { write } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310968.594:10319): arch=c000003e syscall=18
success=no exit=-13 a0=9 a1=7fd3b7947000 a2=1000 a3=9db2d000 items=0
ppid=1 pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107
egid=107 sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
type=AVC msg=audit(1332310968.594:10320): avc: denied { write } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310968.594:10320): arch=c000003e syscall=296
success=no exit=-13 a0=9 a1=2d6c0f8 a2=b a3=18851e000 items=0 ppid=1
pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107 egid=107
sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
type=AVC msg=audit(1332310968.598:10321): avc: denied { write } for
pid=16241 comm="qemu-kvm" path="/var/lib/libvirt/images/vm1.img"
dev=sda1 ino=6431944 scontext=system_u:system_r:svirt_t:s0:c219,c564
tcontext=system_u:object_r:svirt_image_t:s0:c122,c658 tclass=file
type=SYSCALL msg=audit(1332310968.598:10321): arch=c000003e syscall=18
success=no exit=-13 a0=9 a1=7fd383b0f000 a2=1000 a3=18842e000 items=0
ppid=1 pid=16241 auid=0 uid=107 gid=107 euid=107 suid=107 fsuid=107
egid=107 sgid=107 fsgid=107 tty=(none) ses=3 comm="qemu-kvm"
exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c219,c564
key=(null)
restricting vm1 read/write it's own image.
Changing seclabels with virsh/virt-manager is not supported so defined a
new XML with
<seclabel type='dynamic' model='selinux' relabel='no'>
<label>system_u:system_r:svirt_t:s0:c110,c401</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c110,c401</imagelabel>
</seclabel>
but when I try to define it , gives me error :
# virsh define vm3.xml
error: Failed to define domain from vm3.xml
error: unsupported configuration: dynamic label type must use resource
relabeling
looks like it's not possible to assign relabel='no' with dynamic
labelling.
libvirt/src/conf/domain_conf.c :
if (def->type == VIR_DOMAIN_SECLABEL_DYNAMIC &&
def->norelabel) {
virDomainReportError(VIR_ERR_CONFIG_UNSUPPORTED,
"%s", _("dynamic label type must use
resource relabeling"));
goto error;
}
--
Onkar N Mahajan
System Software Engineer,
IBM Linux Technology Center,
Bangalore,India
12 years, 7 months
[libvirt-users] MIPS emulation ....
by William A. Mahaffey III
.... When I query my qemu-mips under FC14 64-bit, libvirt.x86_64
0.8.3-10.fc14, qemu 2:0.13.0-1.fc14, I see the following:
[root@Q6600:/etc, Wed Mar 21, 03:24 PM] 1022 # qemu-mips -cpu ?
MIPS '4Kc'
MIPS '4Km'
MIPS '4KEcR1'
MIPS '4KEmR1'
MIPS '4KEc'
MIPS '4KEm'
MIPS '24Kc'
MIPS '24Kf'
MIPS '34Kf'
[root@Q6600:/etc, Wed Mar 21, 03:24 PM] 1023 #
I don't recognize any of these, I was hoping for either IPnn or
R10k/12k/14k, etc. I would like to try to set up an SGI guest to run
IRIX 5.3 or 6.5.nn to have availability of their compilers. Are these
older CPUs supported under qemu-mips emulation ? Is there some crossover
info on the above listed CPUs (i.e. one of these might in fact be what I
need) ? Has anyone on-list done this ? How did it work out :-) ? TIA for
any pointers ....
--
William A. Mahaffey III
----------------------------------------------------------------------
"The M1 Garand is without doubt the finest implement of war
ever devised by man."
-- Gen. George S. Patton Jr.
12 years, 7 months
[libvirt-users] Number of same HDD-Images
by BrnPnk
Hey,
I set up a new kvm host. (Ubuntu 10.04 x64, up-to-date)
I created a new vm with virt-manager and three hdd-images (raw-format):
- 30 GB (System, virtio)
- 1,7 TB (System, virtio)
- 1,7 TB (System, virtio)
The VM (whatever linux or windows) detects only two of them. When I
change all to IDE -> same problem.
But when change one to IDE and the others to virtio it works. Apparently
only max two images of the same type are detected.
What can I do to use three virtio-devices?
Thanking in anticipation
12 years, 7 months
[libvirt-users] XML syntax for "dir" attribute when making Host directory available to Windows guest
by Cameron Smith
Hi, I have the following setup:
Host: Ubuntu 10.04
Guest: Windows 2008 R2
Kernel: 2.6.32-40-generic
virt-inst: 0.500.1-2ubuntu6.2
qemu-kvm: 0.12.3+noroms-0ubuntu9.18
All is working, however I would now like to share a given directory on the host with the guest. Using the "virsh edit" command I have prepared the following XML configuration snippet:
<filesystem type='mount'>
<source dir='/home/cameron/zip/hla'/>
<target dir='/mnt/hla'/>
</filesystem>
My problem is the "target" element - what value should I use in the "dir" attribute, given that Windows drive paths do not follow Unix format (e.g. "F:\" versus "/mnt/hla").
Can any help?
regards,
cameron
12 years, 7 months
[libvirt-users] Error when executing virsh command to ESX
by li_fuqiong
To Whom It May Concern:
I use virsh windows 0.9.3 to connect an esx server 4.0 with no_verify=1. The Esx server is intel 2 x 3.19 GHZ CPU, 8G memroy and 2 TB hard disk.
following is my execute commands and results.
virsh -c esx://xxx.xxx.xxx.x?no_verify=1
virsh # list all
Id Name State
----------------------------------
80 win2003_122 running
virsh # nodeinfo
error: failed to get node information
error: out of memory
virsh # dumpxml win2003_122
error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp
x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName'
virsh # edit win2003_122
error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp
x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName'
virsh # destroy win2003_122
Domain win2003_122 destroyed
virsh # start win2003_122
Domain win2003_122 started
virsh # edit win2003_122
error: internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp
x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName'
question:
1.Why error when executeing dumpxml and edit command? How to fix it?
2.Why out of memory when nodeinfo. How to fix it? I have only one test vm on my esx server.
Thanks in advance.
Mark
12 years, 7 months
