"phy:/dev/mapper/keys,xvdz,r"
As expected you are using blkback.
hm then it seems that there is a bug in domxml-from-native virsh
translation... I've done the xml config with: virsh domxml-from-native
xen-xl...
On 8/27/20 2:47 PM, Christoph wrote:
Using blkback works for me, e.g. .
what is the diff to 'qemu'?
It's just a different block backend. Xen supports both qemu as a block backend
and blkback. blkback only supports raw IIRC. And apparently, when used with Xen,
the qemu backend only support
Using blkback works for me, e.g. .
what is the diff to 'qemu'?
What xl config did you use? It doesn't work for me if I specify qdisk
and readonly. E.g. the following does not work
"backendtype=qdisk,format=raw,vdev=xvdz,access=ro,target=..."
"phy:/dev/mapper/keys,xvdz,r"
Greetz
On 8/27/20 3:49 AM, Christoph wrote:
Hi All,
I have in config of 2 Xen DomU's this disk:
Using blkback works for me, e.g. .
If I start the DomU's then all starts without problem, see this in log
of the DomU:
{
"pdev_path": "/dev/mapper/keys",
Hi All,
I have in config of 2 Xen DomU's this disk:
If I start the DomU's then all starts without problem, see this in log
of the DomU:
{
"pdev_path": "/dev/mapper/keys",
"vdev": "xvdz",
"backend": "qdisk",
"format":
Hi,
I managed to get SR-IOV with an Intel I350 NIC to work.For this I
followed the documentation on this page:
https://wiki.libvirt.org/page/Networking#Assignment_from_a_pool_of_SRIOV_VFs_in_a_libvirt_.3Cnetwork.3E_definition
But as I have more VMs then VF on the NIC I also have a bridge wich
Daniel P. Berrangé writes:
> On Thu, Aug 27, 2020 at 10:06:25AM +0200, Milan Zamazal wrote:
>> "Daniel P. Berrange" writes:
>>
>
>> > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote:
>> >> Hi,
>> >>
>> >
>> >> we have a problem in oVirt that highly available VMs don't restart aft
On Thu, Aug 27, 2020 at 10:06:25AM +0200, Milan Zamazal wrote:
> "Daniel P. Berrange" writes:
>
> > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote:
> >> Hi,
> >>
> >
> >> we have a problem in oVirt that highly available VMs don't restart after
> >> host poweroff because Vdsm ident
"Daniel P. Berrange" writes:
> On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote:
>> Hi,
>>
>
>> we have a problem in oVirt that highly available VMs don't restart after
>> host poweroff because Vdsm identifies the case as a user initiated
>> shutdown (https://bugzilla.redhat.com/180
On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote:
> Hi,
>
> we have a problem in oVirt that highly available VMs don't restart after
> host poweroff because Vdsm identifies the case as a user initiated
> shutdown (https://bugzilla.redhat.com/1800966).
>
> When poweroff is run on the
10 matches
Mail list logo
